CPU exhaustion via unrestricted TLS renegotiation
Published May 28, 2021 · Updated Aug 3, 2024
Denial of service in SPICE Server before 0.14.92 allows remote attackers to exhaust server CPU through repeated TLS renegotiation. The server's TLS setup accepts client-initiated renegotiation on one connection, repeatedly invoking expensive cryptographic handshake work without limiting requests. No authentication or user interaction is required; a reachable TLS-enabled endpoint can become unresponsive through CPU saturation, without reported data disclosure or modification.
Summary
What happened
Denial of service in SPICE Server before 0.14.92 allows remote attackers to exhaust server CPU through repeated TLS renegotiation. The server's TLS setup accepts client-initiated renegotiation on one connection, repeatedly invoking expensive cryptographic handshake work without limiting requests. No authentication or user interaction is required; a reachable TLS-enabled endpoint can become unresponsive through CPU saturation, without reported data disclosure or modification.
The record
- CVE
- CVE-2021-20201
- Published
- May 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- SPICE
- Product
- SPICE Server
- Classifications
- CWE-400, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=spice 0.14.92
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- THC-SSL-DOSfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo