devalue affected by CPU and memory amplification from sparse arrays
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-770.
Summary
Under certain circumstances, serializing sparse arrays using `uneval` or `stringify` could cause CPU and/or memory exhaustion. When this occurs on the server, it results in a DoS. This is extremely difficult to take advantage of in practice, as an attacker would have to manage to create a sparse array on the server — which is impossible in every mainstream wire format — and then that sparse array would have to be run through `uneval` or `stringify`.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | devalue (npm) | before 5.6.3 | 5.6.3 | Patch available | GHSA-33hq-fvwr-56pm |
- devalue (npm) Vendor— Affected before 5.6.3 Fixed in 5.6.3 Patch available GHSA-33hq-fvwr-56pm
Remediation
- Fix · GHSA-33hq-fvwr-56pm devalue (npm) Fixed in 5.6.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-33hq-fvwr-56pm
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences