CWE-914: Improper Control of Dynamically-Identified Variables

BaseIncomplete

The product does not properly restrict reading from or writing to dynamically-identified variables.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-SpecificInterpreted
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-914 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-914, Improper Control of Dynamically-Identified Variables, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Input Validation controls for Improper Control of Dynamically-Identified Variables

MITRE associates mitigation with Implementation, and Architecture and Design; the listed strategies include Input Validation, and Refactoring; recorded impacts include Modify Application Data, Execute Unauthorized Code or Commands, Varies by Context, and Alter Execution Logic. Use these source-defined anchors to turn CWE-914 into implementation, review, and verification checks for the affected component.

CWE-914: Improper Control of Dynamically-Identified Variables — MITRE CWE

Triage CWE-914 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-914, Improper Control of Dynamically-Identified Variables, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-914

Apply MITRE's full root-cause mapping guidance when using CWE-914, Improper Control of Dynamically-Identified Variables. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-914 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-914, Improper Control of Dynamically-Identified Variables. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-914: Improper Control of Dynamically-Identified Variables?+

CWE-914: Improper Control of Dynamically-Identified Variables is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Control of Dynamically-Identified Variables?+

If exploited, CWE-914 (Improper Control of Dynamically-Identified Variables) it can compromise Integrity and Other, leading to outcomes such as Modify Application Data, Execute Unauthorized Code or Commands, Varies by Context and Alter Execution Logic.

How do you prevent or mitigate Improper Control of Dynamically-Identified Variables?+

Recommended mitigations for CWE-914 include: For any externally-influenced input, check the input against an allowlist of internal program variables that are allowed to be modified. Refactor the code so that internal program variables do not need to be dynamically identified.

Which programming languages are affected by Improper Control of Dynamically-Identified Variables?+

CWE-914 commonly affects Not Language-Specific and Interpreted. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Control of Dynamically-Identified Variables?+

MITRE documents real CVEs mapped to CWE-914, including CVE-2006-7135, CVE-2006-7079, CVE-2007-0649, CVE-2006-6661 and CVE-2006-2828. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-914 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-914

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement