VariantIncomplete

CWE-1321Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Category: other

Description

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

Common consequences· 2

  • Confidentiality / Integrity / Availability — Read Application Data, Modify Application Data
    This weakness is usually exploited by using a special attribute of objects called proto, constructor, or prototype. Such attributes give access to the object prototype. An attacker can inject attributes that are used in other components by adding or modifying attributes of an object prototype. This creates attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the product depends on existence or non-existence of certain attributes, or uses pre-defined attributes of the object prototype (such as hasOwnProperty, toString, or valueOf).
  • Availability — DoS: Crash, Exit, or Restart
    An attacker can override existing attributes with ones that have incompatible type, which may lead to a crash.

Potential mitigations· 5

  • [Implementation]By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
  • [Architecture and Design]By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
  • [Implementation]When handling untrusted objects, validating using a schema can be used.
  • [Implementation]By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.
  • [Implementation]Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.

Related CAPEC attack patterns· 3

CAPEC-1CAPEC-180CAPEC-77

References

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

Exploits (incoming)3

TypeTargetConfidenceTier
AttackPatternManipulating User-Controlled Variablescapec-77100%live
AttackPatternExploiting Incorrectly Configured Access Control Security Levelscapec-180100%live
AttackPatternAccessing Functionality Not Properly Constrained by ACLscapec-1100%live

(incoming)44

TypeTargetConfidenceTier
VulnerabilityCVE-2025-25014cve-2025-250140%live
VulnerabilityCVE-2025-25015cve-2025-250150%live
VulnerabilityCVE-2025-25977cve-2025-259770%live
VulnerabilityCVE-2025-3982cve-2025-39820%live
VulnerabilityCVE-2025-49223cve-2025-492230%live
VulnerabilityCVE-2025-5150cve-2025-51500%live
VulnerabilityCVE-2025-57321cve-2025-573210%live
VulnerabilityCVE-2025-57347cve-2025-573470%live
VulnerabilityCVE-2025-57350cve-2025-573500%live
VulnerabilityCVE-2025-61140cve-2025-611400%live
VulnerabilityCVE-2025-63703cve-2025-637030%live
VulnerabilityCVE-2025-63704cve-2025-637040%live
VulnerabilityCVE-2025-66456cve-2025-664560%live
VulnerabilityCVE-2025-8083cve-2025-80830%live
VulnerabilityCVE-2026-21854cve-2026-218540%live
VulnerabilityCVE-2026-23736cve-2026-237360%live
VulnerabilityCVE-2026-24888cve-2026-248880%live
VulnerabilityCVE-2026-25047cve-2026-250470%live
VulnerabilityCVE-2026-25142cve-2026-251420%live
VulnerabilityCVE-2026-25150cve-2026-251500%live
VulnerabilityCVE-2026-25521cve-2026-255210%live
VulnerabilityCVE-2026-25881cve-2026-258810%live
VulnerabilityCVE-2026-26021cve-2026-260210%live
VulnerabilityCVE-2026-27837cve-2026-278370%live
VulnerabilityCVE-2026-28794cve-2026-287940%live
VulnerabilityCVE-2026-29063cve-2026-290630%live
VulnerabilityCVE-2026-2964cve-2026-29640%live
VulnerabilityCVE-2026-32621cve-2026-326210%live
VulnerabilityCVE-2026-33228cve-2026-332280%live
VulnerabilityCVE-2026-33696cve-2026-336960%live

Showing top 30 of 44 by confidence. Click any target to see the full neighbourhood.

Related by meaning· 6

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

CWE
Improperly Controlled Modification of Dynamically-Determined Object Attributes
CWE
Improper Control of Generation of Code ('Code Injection')
CWE
Insufficient Encapsulation
CWE
Excessive Use of Self-Modifying Code
CWE
Passing Mutable Objects to an Untrusted Method
CWE
Improper Control of Resource Identifiers ('Resource Injection')
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.