Software Supply Chain Failures
Expanded from 'Vulnerable and Outdated Components' to address broader supply chain risks including unknown vulnerabilities introduced by third-parties, compromised packages, and build system attacks.
Overview
New category for 2025. The previous 'Vulnerable and Outdated Components' has evolved to encompass the full spectrum of supply chain risks, including compromised dependencies, typosquatting, and CI/CD pipeline attacks.
How Attackers Exploit This
Understanding attack patterns helps you build better defenses. These are the techniques security teams watch for.
Typosquatting attack
Malicious packages with names similar to popular libraries are published to package registries, hoping developers will install them by mistake.
Compromised maintainer
An attacker gains access to a legitimate package maintainer's account and publishes malicious updates.
Build system compromise
CI/CD pipelines are compromised to inject malicious code during the build process.
How to Prevent
- Remove unused dependencies, features, components, and documentation
- Continuously inventory component versions and their dependencies using SBOM
- Monitor sources like CVE, NVD, and OSV for vulnerabilities in components
- Only obtain components from official sources over secure links
- Verify package integrity using checksums and signatures
- Implement lockfiles and review dependency updates carefully
- Secure CI/CD pipelines with proper access controls and audit logging
- Use dependency scanning tools in your build pipeline
CWEs with Shoulder Detection (2)
These CWEs have Shoulder detection rules. Click to see specific vulnerabilities and fixes.
Other Mapped CWEs (7)
These CWEs are mapped to this category. Use MITRE references for guidance.