CVE-2024-21524: node-stringbuilder vulnerable to Out-of-bounds Read
All versions of the package node-stringbuilder are vulnerable to Out-of-bounds Read due to incorrect memory length calculation, by calling ToBuffer, ToString, or CharAt on a StringBuilder object with a non-empty string value input. It's possible to return previously allocated memory, for example, by providing negative indexes, leading to an Information Disclosure.
Published Jul 10, 2024 · Updated Aug 9, 2024
Affected packages
node-stringbuilder
- Ecosystem
- npm
- Affected
- <= 2.2.7
- Fixed in
- No patched version yet
- Check
npm ls node-stringbuilder
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
All versions of the package node-stringbuilder are vulnerable to Out-of-bounds Read due to incorrect memory length calculation, by calling ToBuffer, ToString, or CharAt on a StringBuilder object with a non-empty string value input. It's possible to return previously allocated memory, for example, by providing negative indexes, leading to an Information Disclosure.
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-21524
- https://gist.github.com/dellalibera/0bb022811224f81d998fa61c3175ee67
- https://security.snyk.io/vuln/SNYK-JS-NODESTRINGBUILDER-6421617
- https://github.com/magiclen/node-stringbuilder/blob/5c2797d3d6bf8cb6d10fe1e077609cef9a5a7de0/src/node-stringbuilder.c#L1281
- https://github.com/advisories/GHSA-g533-xq5w-jmf3
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
