BaseIncomplete

CWE-914Improper Control of Dynamically-Identified Variables

Category: other

Description

The product does not properly restrict reading from or writing to dynamically-identified variables. Many languages offer powerful features that allow the programmer to access arbitrary variables that are specified by an input string. While these features can offer significant flexibility and reduce development time, they can be extremely dangerous if attackers can modify unintended variables that have security implications.

Common consequences· 3

  • Integrity — Modify Application Data
    An attacker could modify sensitive data or program variables.
  • Integrity — Execute Unauthorized Code or Commands
  • Other / Integrity — Varies by Context, Alter Execution Logic

Potential mitigations· 2

  • [Implementation]For any externally-influenced input, check the input against an allowlist of internal program variables that are allowed to be modified.
  • [Implementation, Architecture and Design]Refactor the code so that internal program variables do not need to be dynamically identified.

References

  1. https://cwe.mitre.org/data/definitions/914.html

(incoming)2

TypeTargetConfidenceTier
VulnerabilityCVE-2025-14051cve-2025-140510%live
VulnerabilityCVE-2025-14085cve-2025-140850%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Control of Dynamically-Managed Code Resources
CWE
Improper Control of Resource Identifiers ('Resource Injection')
CWE
Improperly Controlled Modification of Dynamically-Determined Object Attributes
CWE
Access to Critical Private Variable via Public Method
CWE
Improper Adherence to Coding Standards
CWE
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.