Skip to content
Fencer Intel
medium 6.5

CVE-2018-21270 json

Out-of-bounds Read in stringstream

published 7y ago modified 4mo ago also GHSA-mf6x-7mm4-x2g7 , EUVD-2019-0549

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

Summary

Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).

Patch / fix

  • npm stringstream 0.0.6
  • nodejs node.js 0.0.6
  • node-stringstream Debian 14, Debian 13, Debian 12 0.0.6-1

debian advisories DEBIAN-CVE-2018-21270

Is CVE-2018-21270 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-21270 updated cvss 6.5

nodejs-stringstream: out-of-bounds read leading to uninitialized memory exposure

  • 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 OpenShift Container Platform 3.11 kibana Red Hat OpenShift Container Platform 4 kibana, openshift4/ose-logging-kibana6, openshift4/ose-metering-hadoop
    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.68% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/321670 referenced PoC, tagged "exploit" by a source, unverified
  • npmjs.com https://www.npmjs.com/advisories/664 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P

Affected packages

ecosystem package affected fixed in
npm stringstream
<0.0.6
0.0.6

Classification

Weakness
Technology feeds

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.