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

Description

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.

[object Object]

Common consequences

• 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

• Implementation
  [object Object]
• Architecture and Design,Implementation
  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.
• Implementation
  For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
• Implementation,Architecture and Design
  Refactor the code so that object attributes or fields do not need to be dynamically identified, and only expose getter/setter functionality for the intended attributes.

Related CWEs

Recent CVEs classified under this CWE