Vulnerability Database · npm · stringstream · Version
stringstream 0.0.1
0.0.1 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.0.0.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 23 Jun 2012
Licence non-standard
Also known from other sources 1
Newer releases 8
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
stringstream 0.0.1 vulnerabilities
2 vulnerabilities cover stringstream 0.0.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Out-of-Bounds Read Vulnerability in Node.js stringstream | 6.5 medium | 0.0.6 | 06 Jan 2022 |
| CVE-2018-21270: Out-of-bounds Read in stringstream | N/A medium | 0.0.6 | 20 Jun 2019 |
Looking for another version, or everything Vulert holds for stringstream?
Questions
About stringstream 0.0.1
Is stringstream 0.0.1 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover stringstream 0.0.1: 0 critical, 0 high, 2 medium and 0 low. The upgrade Vulert recommends is 1.0.0, and each entry above names the fixed version to move to.
Which version of stringstream should I use instead of 0.0.1?
1.0.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.0.1 the latest release of stringstream?
No. 0.0.1 was published 23 Jun 2012, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor stringstream for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the stringstream version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.