CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes

BaseIncomplete

The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

View on MITRE
Back to CWE Lookup

Extended Description

If the object contains attributes that were only intended for internal use, then their unexpected modification could lead to a vulnerability. This weakness is sometimes known by the language-specific mechanisms that make it possible, such as mass assignment, autobinding, or object injection.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
RubyASP.NETPHPPythonNot Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-915 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-915, Improperly Controlled Modification of Dynamically-Determined Object Attributes, 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 Improperly Controlled Modification of Dynamically-Determined Object Attributes

MITRE associates mitigation with Implementation, and Architecture and Design; the listed strategies include Input Validation, and Refactoring; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-915 into implementation, review, and verification checks for the affected component.

CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes — MITRE CWE

Triage CWE-915 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-915, Improperly Controlled Modification of Dynamically-Determined Object Attributes, 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-915

Apply MITRE's full root-cause mapping guidance when using CWE-915, Improperly Controlled Modification of Dynamically-Determined Object Attributes. 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-915 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-915, Improperly Controlled Modification of Dynamically-Determined Object Attributes. 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-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes?+

CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. If the object contains attributes that were only intended for internal use, then their unexpected modification could lead to a vulnerability. This weakness is sometimes known by the language-specific mechanisms that make it possible, such as mass assignment, autobinding, or object injection.

What are the security consequences of Improperly Controlled Modification of Dynamically-Determined Object Attributes?+

If exploited, CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes) 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 Improperly Controlled Modification of Dynamically-Determined Object Attributes?+

Recommended mitigations for CWE-915 include: If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment. If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified. For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.

Which programming languages are affected by Improperly Controlled Modification of Dynamically-Determined Object Attributes?+

CWE-915 commonly affects Ruby, ASP.NET, PHP, Python and Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improperly Controlled Modification of Dynamically-Determined Object Attributes?+

MITRE documents real CVEs mapped to CWE-915, including CVE-2024-3283, CVE-2012-2054, CVE-2012-2055, CVE-2008-7310 and CVE-2013-1465. 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-915 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-915

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