2 known bugs in nanoid, with affected versions, fixes and workarounds. Sourced from upstream issue trackers.
| Severity | Affected | Fixed in | Title | Status | Source |
|---|---|---|---|---|---|
| medium | 3.0.0 | 3.1.31 | Exposure of Sensitive Information to an Unauthorized Actor in nanoid The package nanoid from 3.0.0, before 3.1.31, are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated. | fixed | osv:GHSA-qrpm-p2h7-hrv2 |
| medium | 4.0.0 |
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/bugs/npm/nanoid| 5.0.9 |
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. |
| fixed |
| osv:GHSA-mwcw-c2x4-8c55 |