CVE-2020-35896
published 2020-12-31CVE-2020-35896: An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.
PriorityP337high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
1.34%
67.7th percentile
An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| ws-rs_project | ws-rs | <= 0.9.1 | — |
| ws_project | ws | 0 – 0.9.1 | — |
| ws_project | ws | >= 0.0.0-0 | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Insufficient size checks in ws
osv·2021-08-25
CVE-2020-35896 [HIGH] Insufficient size checks in ws
Insufficient size checks in ws
An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.
GHSA
Insufficient size checks in ws
ghsa·2021-08-25
CVE-2020-35896 [HIGH] CWE-400 Insufficient size checks in ws
Insufficient size checks in ws
An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.
OSV
Insufficient size checks in outgoing buffer in ws allows remote attacker to run the process out of memory
osv·2020-09-25
CVE-2020-35896 Insufficient size checks in outgoing buffer in ws allows remote attacker to run the process out of memory
Insufficient size checks in outgoing buffer in ws allows remote attacker to run the process out of memory
Affected versions of this crate did not properly check and cap the growth of the outgoing buffer.
This allows a remote attacker to take down the process by growing the buffer of their (single) connection until the process runs out of memory it can allocate and is killed.
The flaw was corrected in the [`parity-ws` fork](https://crates.io/crates/parity-ws) (>=0.10.0) by [disconnecting a client when the buffer runs full](https://github.com/housleyjk/ws-rs/pull/328).
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2020-12-31
Published