LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23442: Prototype Pollution

This affects all versions of package @cookiex/deep. The global proto object can be polluted using the __proto__ object.

HighCVSS 8.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-23442 is a prototype pollution issue in the JavaScript package @cookiex/deep. If an application processes attacker-controlled objects through this library, shared JavaScript object behavior may be altered, creating risk of data exposure, logic manipulation, or service disruption.

Executive priority

Prioritize remediation where @cookiex/deep is present in internet-facing services or request-processing paths. Treat this as high urgency for exposed applications, but do not assume active exploitation from the provided sources.

Technical view

The package @cookiex/deep is reported vulnerable in all versions because __proto__ handling can pollute the global prototype object. CVSS 3.1 is 8.6, with network attack vector, low complexity, no privileges, and no user interaction. The sources reference an upstream issue and commit, but no fixed release is identified in the bundle.

Likely exposure

Exposure is most likely in Node.js or frontend build projects that depend on @cookiex/deep and pass untrusted nested objects, JSON, or request data into its deep object operations.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitability is plausible from the CVSS vector and Snyk advisory context, but operational exploitation status is unconfirmed.

Researcher notes

Evidence supports a __proto__ prototype pollution flaw and an upstream fix reference, but the bundle does not name a safe release version. Validate reachability in application code before assigning exploitability beyond dependency presence.

Mitigation direction

  • Inventory JavaScript projects and lockfiles for direct or transitive use of @cookiex/deep.
  • Upgrade to a vendor-supported fixed release if available; otherwise replace the dependency.
  • Confirm the referenced GitHub fix is included before treating any version as remediated.
  • Avoid passing untrusted JSON or request bodies into vulnerable deep object operations.
  • Monitor Snyk and upstream repository guidance for maintained remediation details.

Validation and detection

  • Check software composition analysis results for @cookiex/deep in production and build-time applications.
  • Review whether user-controlled input reaches @cookiex/deep deep merge or object manipulation paths.
  • Verify remediation by confirming the vulnerable dependency is removed or contains the upstream fix.
  • Regression test affected workflows for authorization, object defaults, and configuration handling after remediation.
Prepared
Confidence
medium
Sources
5

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-23442 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
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L/E:P/RL:O/RC:R

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
4Source 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
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L/E:P/RL:O/RC:R3.94.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2021-23442Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L/E:P/RL:O/RC:R

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/a@cookiex/deep0Listed
Weakness

CWE details

No CWE listed

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