Third-Party Dependencies With Known Vulnerabilities
The application includes third-party libraries or packages at versions with publicly known vulnerabilities, some of which may be exploitable through the application.
| Severity | Medium |
| CVSS 3.1 | 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application |
| Category | Outdated Components |
Description
The application includes open source or commercial libraries, frameworks or packages at versions affected by publicly disclosed vulnerabilities for which fixed versions are available. This applies to server-side packages, for example from npm, PyPI, Maven, NuGet, RubyGems or Composer, to client-side JavaScript libraries served to browsers, and to the dependencies of those dependencies, which often outnumber the packages the developers chose directly and are easily overlooked. What an attacker can do depends on the vulnerable component and how the application uses it, and ranges from cross-site scripting through an outdated client-side library to remote code execution through a server-side framework or parser.
Not every reported vulnerability is exploitable: many affect only a function or configuration that the application does not use. Where a vulnerable function is reachable with input an attacker controls, published details and exploit code make exploitation straightforward, and widely used components are scanned for at internet scale. Where the vulnerable code is not reachable, the immediate risk is low, but the outdated component makes future fixes harder to apply quickly.
The weakness is identified by software composition analysis tools such as OWASP Dependency-Check, npm audit, pip-audit or the hosting platform's dependency alerts, which compare the declared and resolved package versions with vulnerability databases, or during testing from version strings in served files. Each finding needs triage to decide whether the vulnerable code is reachable, and vulnerabilities listed in CISA's Known Exploited Vulnerabilities catalogue, or with public exploit code, deserve priority.
Remediation
Update the affected components and put dependency management on a continuous footing:
- Upgrade each affected dependency to a version that fixes the reported vulnerabilities, including transitive dependencies, using the package manager's override or resolution feature where a direct dependency has not yet updated. Replace components that are no longer maintained.
- Commit lock files so that builds use known versions, and rebuild and redeploy after updating; for client-side libraries, update the files actually served to browsers.
- Add software composition analysis to the CI/CD pipeline and the repository so that changes introducing or keeping vulnerable versions are flagged, and use automated update tools to raise upgrade requests.
- Maintain a software bill of materials (SBOM) for each application, so that newly disclosed vulnerabilities can be matched to affected systems quickly.
- Set target times for fixing by severity, with known exploited vulnerabilities fixed first.
Where an upgrade cannot be made quickly, record the reason, confirm whether the vulnerable code is reachable, and consider a compensating control such as a web application firewall rule for the specific flaw. Confirm the fix by rerunning the composition analysis against the built application and checking that the reported versions are no longer present.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.