CVE-2018-21270
Out-of-bounds Read in stringstream
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).
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
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).
- Record
CVE-2018-21270- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H - CVSS 2.0
- 5.8 Medium
AV:N/AC:M/Au:N/C:P/I:N/A:P - Weakness
- CWE-125
- Updated
- 2026-11-02
CVE List No score
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).
- Record
CVE-2018-21270- Updated
- 2026-11-02
EUVDEUVD-2019-0549 No score
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).
- Record
EUVD-2019-0549- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-mf6x-7mm4-x2g7 No score
Out-of-bounds Read in stringstream
All versions of stringstream are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.
Recommendation
No fix is currently available for this vulnerability. It is our recommendation to not install or use this module if user input is being passed in to stringstream.
- Record
GHSA-mf6x-7mm4-x2g7- Weakness
- CWE-125
- Updated
- 2026-11-02
OSV
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).
- Record
CVE-2018-21270- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2018-21270
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).
- Record
DEBIAN-CVE-2018-21270- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
Show 4 moreShow less
OSVUBUNTU-CVE-2018-21270
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).
- Record
UBUNTU-CVE-2018-21270- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVCLSA-2026-1772583200 No score
TuxCare security update for stringstream (1 CVE)
TuxCare rebuilt stringstream to address 1 CVE. Fixed in 0.0.5-tuxcare.1.
- Record
CLSA-2026-1772583200- Updated
- 2026-11-02
OSVCLSA-2026-1773274557 No score
TuxCare security update for stringstream (1 CVE)
TuxCare rebuilt stringstream to address 1 CVE. Fixed in 0.0.4-tuxcare.1.
- Record
CLSA-2026-1773274557- Updated
- 2026-11-02
OSVGHSA-mf6x-7mm4-x2g7 No score
Out-of-bounds Read in stringstream
All versions of stringstream are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.
Recommendation
No fix is currently available for this vulnerability. It is our recommendation to not install or use this module if user input is being passed in to stringstream.
- Record
GHSA-mf6x-7mm4-x2g7- Weakness
- CWE-125
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
stringstreamnpm |
before 0.0.6 | 0.0.6 |
stringstreamTuxCare:npm |
0.0.5-tuxcare.0 up to 0.0.5-tuxcare.1, plus listed versions 0.0.5 |
0.0.5-tuxcare.1 |
stringstreamTuxCare:npm |
0.0.4-tuxcare.0 up to 0.0.4-tuxcare.1, plus listed versions 0.0.4 |
0.0.4-tuxcare.1 |
node-stringstreamDebian:12 |
before 0.0.6-1 | 0.0.6-1 |
node-stringstreamDebian:13 |
before 0.0.6-1 | 0.0.6-1 |
node-stringstreamDebian:14 |
before 0.0.6-1 | 0.0.6-1 |
node-stringstreamUbuntu:18.04:LTS |
All versions, plus listed versions 0.0.5-1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2018-21270 is a medium vulnerability (CVSS 6.5) in Nodejs Node.js, published June 20, 2019. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 3.68%, the 89th percentile. Fixed in stringstream 0.0.6.
References
hackerone.com/reports/321670
npmjs.com/advisories/664
github.com/mhart/StringStream/issues/7
security-tracker.debian.org/tracker/CVE-2018-21270
ubuntu.com/security/CVE-2018-21270
cve.org/CVERecord?id=CVE-2018-21270