CWE WEAKNESSES / CWE-913
CWE-913
Improper Control of Dynamically-Managed Code Resources
What it is
The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
Many languages offer powerful features that allow the programmer to dynamically create or modify existing code, or resources used by code such as variables and objects. While these features can offer significant flexibility and reduce development time, they can be extremely dangerous if attackers can directly influence these code resources in unexpected ways.
Impact
| Integrity | Execute Unauthorized Code or Commands |
| Other, Integrity | Varies by Context, Alter Execution Logic |
Mitigations
- [Implementation] For any externally-influenced input, check the input against an allowlist of acceptable values.
- [Implementation, Architecture and Design] Refactor the code so that it does not need to be dynamically managed.
Real-world CVE examples
- CVE-2022-2054 — Python compiler uses eval() to execute malicious strings as Python code.
- CVE-2018-1000613 — Cryptography API uses unsafe reflection when deserializing a private key
- CVE-2015-8103 — Deserialization issue in commonly-used Java library allows remote execution.
- CVE-2006-7079 — Chain: extract used for register_globals compatibility layer, enables path traversal (CWE-22)
- CVE-2012-2055 — Source version control product allows modification of trusted key using mass assignment.
Related weaknesses
Browse all common weaknesses, check related exploited CVEs, or map to ATT&CK techniques.
Source: MITRE CWE. View on cwe.mitre.org →