Skip to content
Fencer Intel
critical 9.8

CVE-2018-16492 json

Prototype Pollution in extend

published 7y ago modified 4mo ago also GHSA-qrmc-fj45-qfc2 , EUVD-2019-0333

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

A prototype pollution vulnerability was found in module extend <2.0.2, ~<3.0.2 that allows an attacker to inject arbitrary properties onto Object.prototype.

Patch / fix

  • npm extend 2.0.2, 3.0.2
  • extend_project extend 2.0.2, 3.0.2
  • node-extend Debian 14, Debian 13, Debian 12 3.0.2-1

debian advisories DEBIAN-CVE-2018-16492

Is CVE-2018-16492 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-16492 updated cvss 4.8

nodejs-extend: Prototype pollution can allow attackers to modify object properties

  • Red Hat Software Collections rh-nodejs6-nodejs-extend
    affected: no fix planned “Will not fix”
  • Red Hat Quay v3 quay/quay-rhel8 v3.6.0-62
    fixed: vendor fix RHSA-2021:3917
  • Red Hat Quay v3 quay/clair-rhel8 v3.6.0-70, quay/quay-builder-rhel8 v3.6.0-44, quay/quay-operator-rhel8 v3.6.0-43, quay/quay-operator-bundle v3.6.0-48, quay/quay-bridge-operator-rhel8 v3.6.0-40, quay/quay-bridge-operator-bundle v3.6.0-35, +3 more Red Hat Mobile Application Platform 4 nodejs-extend Red Hat OpenShift Container Platform 3.10 logging-kibana, logging-auth-proxy, jenkins-slave-nodejs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.05% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/381185 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
npm extend
>=3.0.0, <3.0.2
>=1.1.3, <2.0.2
3.0.2
2.0.2

Affected products

  • HackerOne extend

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.