Friday, March 29, 2024

A-9 Using Components with known Vulnerabilities – Every Developers Should aware

Exploitability of the risk is average, Attacker needs to identify the weak part through scanning or manual analysis.

But the risk is widely spread, Many application has these issues on the grounds that most development teams don’t concentrate on guaranteeing their parts/libraries are breakthrough.

Most of the time, the developers don’t know every one of the parts they are utilizing, it doesn’t mind their formats.

A full range of weaknesses is possible, including injection, broken access control, XSS, etc. The impact could range from minimal to complete.

SCENARIO 1:

A-9 Using Components with known Vulnerabilities

Now the attacker and the webserver, the attacker tries to exploit a vulnerable component on the server, a Vulnerable component is nothing but a product or Library which could be at risk.

SCENARIO 2:

A-9 Using Components with known Vulnerabilities
  1. In this scenario, the attacker tries to make a request to the website, and let’s assume this request loads a page which has the vulnerability.
  2. The website responds to the request which also discloses the vulnerable components.
  3. Once the attacker finds the vulnerable components and version, then he will go to Internet and searches for known vulnerabilities.
  4. Regardless it is easy to find risks associated with vulnerable components on the web, so the attackers get information on how this risk might be exploited.
  5. Then attacker so goes and launches the attack with the website.

Common Defences

  • Identify Components and versions.
  • Components that are used unplanned.
  • Monitor CVEs impacting those components.
  • Keep Components updated.
  • Regularly Monitor new releases.
Website

Latest articles

How to Analyse .NET Malware? – Reverse Engineering Snake Keylogger

Utilizing sandbox analysis for behavioral, network, and process examination provides a foundation for reverse...

GoPlus’s Latest Report Highlights How Blockchain Communities Are Leveraging Critical API Security Data To Mitigate Web3 Threats

GoPlus Labs, the leading Web3 security infrastructure provider, has unveiled a groundbreaking report highlighting...

Wireshark 4.2.4 Released: What’s New!

Wireshark stands as the undisputed leader, offering unparalleled tools for troubleshooting, analysis, development, and...

Zoom Unveils AI-Powered All-In-One AI Work Workplace

Zoom has taken a monumental leap forward by introducing Zoom Workplace, an all-encompassing AI-powered...

iPhone Users Beware! Darcula Phishing Service Attacking Via iMessage

Phishing allows hackers to exploit human vulnerabilities and trick users into revealing sensitive information...

2 Chrome Zero-Days Exploited at Pwn2Own 2024: Patch Now

Google has announced a crucial update to its Chrome browser, addressing several vulnerabilities, including...
Guru baran
Guru baranhttps://gbhackers.com
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Mitigating Vulnerability Types & 0-day Threats

Mitigating Vulnerability & 0-day Threats

Alert Fatigue that helps no one as security teams need to triage 100s of vulnerabilities.

  • The problem of vulnerability fatigue today
  • Difference between CVSS-specific vulnerability vs risk-based vulnerability
  • Evaluating vulnerabilities based on the business impact/risk
  • Automation to reduce alert fatigue and enhance security posture significantly

Related Articles