CWE-913 Improper Control of Dynamically-Managed Code Resources

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.

• Integrity: Execute Unauthorized Code or Commands • Other, Integrity: Varies by Context, Alter Execution Logic

• [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.

• Fuzzing: 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.

• 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.