nodejs-stringstream: out-of-bounds read leading to uninitialized memory exposure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Quay 3 | |||
| quay/quay-rhel8:v3.6.0-62 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:3917 | 2021-10-19T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-0549 | 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). |
Github GHSA |
GHSA-mf6x-7mm4-x2g7 | Out-of-bounds Read in stringstream |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.7% (3.682% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.