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.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| ChildOf | Discouraged | P | 664 | Improper Control of a Resource Through its Lifetime |
| ParentOf | Allowed | B | 470 | Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') |
| ParentOf | Allowed | B | 502 | Deserialization of Untrusted Data |
| ParentOf | Allowed | B | 914 | Improper Control of Dynamically-Identified Variables |
| ParentOf | Allowed | B | 915 | Improperly Controlled Modification of Dynamically-Determined Object Attributes |
| ParentOf | Allowed-with-Review | B | 94 | Improper Control of Generation of Code ('Code Injection') |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | V | 1003 | Weaknesses for Simplified Mapping of Published Vulnerabilities |
| MemberOf | Prohibited | C | 1345 | OWASP Top Ten 2021 Category A01:2021 - Broken Access Control |
| MemberOf | Prohibited | C | 1416 | Comprehensive Categorization: Resource Lifecycle Management |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-279 | Input Validation Strategy |
| MemberOf | Prohibited | BS | BOSS-281 | Refactoring Strategy |
| MemberOf | Prohibited | BS | BOSS-311 | Execute Unauthorized Code or Commands (impact) |
| MemberOf | Prohibited | BS | BOSS-326 | Varies by Context (impact) |
| MemberOf | Prohibited | BS | BOSS-330 | Alter Execution Logic (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1345 | OWASP Top Ten 2021 Category A01:2021 - Broken Access Control |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Integrity | N/A | Execute Unauthorized Code or Commands | N/A |
| OtherIntegrity | N/A | Varies by ContextAlter Execution Logic | N/A |
For any externally-influenced input, check the input against an allowlist of acceptable values.
Refactor the code so that it does not need to be dynamically managed.
N/A
N/A
| Reference | Description |
|---|---|
| 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. |
| Ordinality | Description |
|---|
Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
N/A
This CWE entry is a Class and might have Base-level children that would be more appropriate
Examine children of this entry to see if there is a better fit
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|
| ID | Name |
|---|