LiveActive security incident?Get immediate response
CVE Record

CVE-2018-16486: A prototype pollution vulnerability was found in defaults-deep <=0.2.4 that would allow a malicious user to...

A prototype pollution vulnerability was found in defaults-deep <=0.2.4 that would allow a malicious user to inject properties onto Object.prototype.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-16486 affects the npm package defaults-deep through version 0.2.4. A malicious input could add properties to JavaScript’s shared Object prototype, potentially changing application behavior. Business risk depends on where the package is used and whether untrusted data reaches it. No source provided indicates known active exploitation.

Executive priority

Treat as a targeted dependency hygiene issue, not an emergency based on current evidence. Prioritize applications exposed to untrusted users or handling sensitive authorization logic. Remediate during normal vulnerability management unless internal exposure analysis shows critical business impact.

Technical view

The issue is prototype pollution in HackerOne defaults-deep <=0.2.4, allowing property injection onto Object.prototype. The CVE record lists CWE-400 and no CVSS score. Impact is application-dependent: polluted prototype properties may cause logic errors, denial of service, or security control bypass in consuming applications.

Likely exposure

Exposure is most likely in Node.js applications or build/runtime dependencies that include defaults-deep <=0.2.4, directly or transitively. Systems not using this package are not affected based on the provided sources.

Exploitation context

The public description states that a malicious user can inject properties onto Object.prototype. The provided sources do not state active exploitation, public weaponization, or inclusion in CISA KEV. Practical impact depends on application data flow and trust boundaries.

Researcher notes

Evidence is sparse: CVE metadata, affected version range, and a HackerOne report reference. No CVSS, patch version, exploit status, or detailed impact is provided in the supplied bundle. Validate exposure through dependency analysis and application-specific data-flow review.

Mitigation direction

  • Inventory Node.js projects for defaults-deep <=0.2.4.
  • Check npm lockfiles and SBOMs for direct or transitive use.
  • Review vendor or package maintainer guidance for fixed versions.
  • Upgrade or replace the package where a maintained safe version is available.
  • Prioritize internet-facing applications processing untrusted input.

Validation and detection

  • Confirm whether defaults-deep appears in package manifests, lockfiles, or SBOMs.
  • Verify installed versions are not <=0.2.4.
  • Identify code paths where untrusted input reaches dependency merging behavior.
  • After remediation, regenerate lockfiles and confirm dependency resolution changed.
  • Monitor vendor advisories for updated remediation details.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-16486 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnedefaults-deep<=0.2.4Listed
Weakness

CWE details

CWE-400

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