LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23434: Prototype Pollution

This affects the package object-path before 0.11.6. A type confusion vulnerability can lead to a bypass of CVE-2020-15256 when the path components used in the path parameter are arrays. In particular, the condition currentPath === '__proto__' returns false if currentPath is ['__proto__']. This is because the === operator returns always false when the type of the operands is different.

MediumCVSS 5.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-23434 is a prototype pollution issue in the object-path package before 0.11.6. If an application lets untrusted input shape object paths, an attacker may influence object behavior or data handling. The public bundle does not show active exploitation or KEV listing.

Executive priority

Treat as a dependency hygiene issue with moderate urgency. Prioritize internet-facing or multi-tenant applications that process user-controlled JSON or path-like input, but do not treat it as an emergency absent exploitation evidence.

Technical view

A type confusion flaw can bypass the CVE-2020-15256 protection when path components are arrays. The check for '__proto__' fails because strict equality compares different operand types. The stated impact is low confidentiality, integrity, and availability impact with high attack complexity.

Likely exposure

Exposure is most likely in JavaScript, Node.js, WebJars, or Debian environments that include object-path before 0.11.6, directly or transitively. Risk depends on whether attacker-controlled path data reaches object-path operations.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not cite active exploitation. Practical risk is application-specific because exploitation depends on vulnerable package versions and controllable path components.

Researcher notes

The key technical detail is the array path component bypass of a prior prototype pollution fix. The bundle lists no CWE and provides no proof of exploitation. Validate reachability before escalating severity beyond dependency remediation.

Mitigation direction

  • Upgrade object-path to 0.11.6 or later where applicable.
  • Update WebJars or Debian node-object-path packages per vendor advisories.
  • Regenerate lockfiles after dependency updates.
  • Check vendor guidance if ecosystem version mapping is unclear.
  • Reduce or validate untrusted inputs used as object paths.

Validation and detection

  • Search dependency manifests and lockfiles for object-path versions before 0.11.6.
  • Run software composition analysis across direct and transitive dependencies.
  • Check Debian package status where node-object-path is installed.
  • Review code paths passing external input into object-path APIs.
  • Confirm updated builds no longer resolve vulnerable versions.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-23434 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L2.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.6Medium
CVSS 3.1 vector shape for CVE-2021-23434Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aobject-pathunspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.