CWE-99: Improper Control of Resource Identifiers ('Resource Injection')
low-riskThe product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control.
Abstraction: Class
Common Consequences
Confidentiality
→
Read Application Data
Detection Methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2019-6545 | 7.5 | 18.7% | — |
| CVE-2024-5706 | 8.8 | 3.9% | — |
| CVE-2016-8615 | 5.3 | 2.3% | — |
| CVE-2021-22879 | 8.8 | 2.2% | — |
| CVE-2025-0756 | 9.1 | 1.7% | — |
| CVE-2022-39369 | 8.0 | 0.9% | — |
| CVE-2017-5159 | 9.8 | 0.7% | — |
| CVE-2022-27670 | 6.5 | 0.6% | — |
| CVE-2022-3774 | 5.4 | 0.5% | — |
| CVE-2024-0231 | 2.7 | 0.4% | — |
1
/ 100
low-risk
Active Threat
1/50 · Minimal
Exploit Availability
0/50 · Minimal