CWE-913

Improper Control of Dynamically-Managed Code Resources

Weakness Description

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.

Potential Mitigations

Implementation

For any externally-influenced input, check the input against an allowlist of acceptable values.

ImplementationArchitecture and Design

Refactor the code so that it does not need to be dynamically managed.

Common Consequences

Integrity
Execute Unauthorized Code or Commands
OtherIntegrity
Varies by ContextAlter Execution Logic

Detection Methods

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.

Effectiveness: High

Advertisement

Related Weaknesses