Predictable results in nanoid generation when given non-integer values
When nanoid is called with a fractional value, there were a number of undesirable effects: 1. in browser and non-secure, the code infinite loops on while (size--) 2. in node, the value of poolOffset becomes fractional, causing calls to nanoid to return zeroes until the pool is next filled 3. if the first call in node is a fractional argument, the initial buffer allocation fails with an error Version 3.3.8 and 5.0.9 are fixed.
01
describes (1)
Related CVEs.
| ID | severity | exploitable |
|---|---|---|
| CVE-2024-55565US | — | — |
02
references
External citations — patches, advisories, analysis.
- https://github.com/ai/nanoidPACKAGE
- https://github.com/ai/nanoid/compare/3.3.7...3.3.8WEB
- https://github.com/ai/nanoid/pull/510WEB
- https://github.com/ai/nanoid/releases/tag/5.0.9WEB
- https://lists.debian.org/debian-lts-announce/2024/12/msg00025.htmlWEB
- https://lists.debian.org/debian-lts-announce/2025/01/msg00006.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-55565ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan