ws: Memory exhaustion DoS from tiny fragments and data chunks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- websockets ws
From 1.1.0 · fixed in 5.2.5; From 6.0.0 · fixed in 6.2.4; From 7.0.0 · fixed in 7.5.11; From 8.0.0 · fixed in 8.21.0
- wsnpm
From 1.1.0 · fixed in 5.2.5
- wsnpm
From 6.0.0 · fixed in 6.2.4
- wsnpm
From 7.0.0 · fixed in 7.5.11
- wsnpm
From 8.0.0 · fixed in 8.21.0