Supply-Chain Vulnerability
Also called dependency vulnerability.
A flaw introduced through a third-party component or dependency.
What it is
A vulnerability inherited from external code, libraries, build tooling, or vendors rather than written in-house. A single compromised or vulnerable dependency can affect every product that includes it.
Why it matters
Supply-chain issues turn one upstream flaw into widespread, hard-to-track exposure across many downstream consumers. Software composition analysis and dependency inventories are how teams find and prioritize them.
In practice
A widely used open-source library ships a vulnerable function, exposing every application that bundled that version.
What to look for
- Vulnerable dependencies in your build.
- Software bills of materials for what you ship.
- Packages from new or changed maintainers.
Common mistake
Scanning only your own code. Most of what you ship comes from dependencies.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Trivy Open source
Scans images, file systems and code for known vulnerabilities and secrets.
-
Falco Open source
Detects suspicious behavior inside running containers and Kubernetes.
-
Sigstore Open source
Signs and verifies software artifacts so you can prove where a build came from.
-
CrowdStrike Falcon Cloud Security Commercial
Protects cloud workloads and containers, from build to runtime.
Read next
- Insecure Deserialization: Rebuilding objects from untrusted data, enabling code execution.
- Default Credentials: Shipped factory usernames and passwords left unchanged.
- Vulnerability Scanning: Automated probing of systems for known weaknesses.