Vulnerable and Outdated Components
Components such as libraries, frameworks, and other software modules run with the same privileges as the application. If a vulnerable component is exploited, it can cause serious data loss.
Overview
Previously titled Using Components with Known Vulnerabilities. It is #2 in the Top 10 community survey but also had enough data to make the Top 10 via data analysis.
How Attackers Exploit This
Understanding attack patterns helps you build better defenses. These are the techniques security teams watch for.
Known vulnerability exploitation
Attackers target publicly disclosed vulnerabilities in popular libraries before applications are patched.
Supply chain compromise
Malicious code is introduced through compromised or typosquatted packages.
How to Prevent
- Remove unused dependencies, features, components, and documentation
- Continuously inventory component versions and their dependencies
- Monitor sources like CVE and NVD for vulnerabilities in components
- Only obtain components from official sources over secure links
- Monitor for unmaintained libraries that don't receive security patches
- Use virtual patching via web application firewall if needed
CWEs with Shoulder Detection (1)
These CWEs have Shoulder detection rules. Click to see specific vulnerabilities and fixes.
Other Mapped CWEs (2)
These CWEs are mapped to this category. Use MITRE references for guidance.