A03: Software Supply Chain Failures
Supply chain failures occur through vulnerabilities or malicious changes in third-party code, tools, or dependencies. This includes using outdated libraries, unverified packages, and compromised build pipelines.
Key Vulnerabilities
Not tracking versions of all components including transitive dependencies
Using vulnerable, unsupported, or outdated software components
Not scanning for vulnerabilities regularly
Lack of change management in the supply chain
Using components from untrusted sources in production
CI/CD pipeline with weaker security than production systems
Prevention Strategies
Generate and maintain a Software Bill of Materials (SBOM)
Remove unused dependencies and unnecessary features
Continuously inventory component versions with tools like OWASP Dependency Track
Monitor CVE databases and subscribe to security alerts
Only obtain components from official sources over secure links
Use staged rollouts to limit exposure from compromised vendors
Real-World Example
The 2020 SolarWinds supply chain attack compromised ~18,000 organizations by inserting malicious code into a trusted software update. The 2021 Log4Shell vulnerability (CVE-2021-44228) affected millions of systems worldwide.
Code Comparison
// VULNERABLE: Using outdated package with known CVE
{
"dependencies": {
"lodash": "4.17.15", // CVE-2020-8203
"log4j": "2.14.0", // Log4Shell CVE-2021-44228
"random-npm-package": "*" // Wildcard = any version
}
}// SECURE: Pinned versions, audited dependencies
{
"dependencies": {
"lodash": "4.17.21", // Patched version
"pino": "8.16.0", // Alternative to log4j
"@verified/package": "2.1.0" // Scoped, verified
},
"scripts": {
"audit": "npm audit --production",
"check": "npx lockfile-lint --path package-lock.json"
}
}