CVE-2022-30591
Published: 06 July 2022
Summary
CVE-2022-30591 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Quic-Go Project Quic-Go. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 5.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2022-30591 affects quic-go versions through 0.27.0. The root cause is a misparse of the MTU Discovery service inside mtu_discoverer.go that overflows the probe timer, allowing a Slowloris-style attack that sends incomplete QUIC or HTTP/3 requests and drives sustained CPU consumption. The flaw is tracked as CWE-400 and carries a CVSS 3.1 score of 7.5.
Remote attackers with no credentials or user interaction can exploit the issue across the network to produce a denial-of-service condition that degrades or halts service availability. The attack requires only the ability to initiate QUIC or HTTP/3 sessions.
The vendor states that the observed behavior should not be recorded as a vulnerability on the CVE List. No patch or mitigation guidance appears in the supplied references, which consist solely of links to the affected source file. The associated EPSS score stands at 0.1510 with no indicated rise from an earlier lower value.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-52434
Vulnerability details
quic-go through 0.27.0 allows remote attackers to cause a denial of service (CPU consumption) via a Slowloris variant in which incomplete QUIC or HTTP/3 requests are sent. This occurs because mtu_discoverer.go misparses the MTU Discovery service and consequently overflows the…
more
probe timer. NOTE: the vendor's position is that this behavior should not be listed as a vulnerability on the CVE List
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Limiting concurrent sessions directly prevents uncontrolled resource consumption by capping the number of active sessions per user or account.
Analysis identifies uncontrolled resource consumption indicative of denial-of-service or abuse attempts.
Contingency plan testing includes resource exhaustion scenarios to verify recovery, making it harder for attackers to sustain exploits that cause uncontrolled consumption.
Updated contingency plans include current procedures to detect, contain, and recover from resource exhaustion, limiting an attacker's ability to sustain impact from uncontrolled consumption.
Alternate site allows resumption of operations if resource exhaustion at the primary site is exploited to cause unavailability.
Alternate telecommunications services enable resumption of essential functions when primary services become unavailable due to uncontrolled resource consumption.
The team can analyze and respond to resource exhaustion incidents, reducing the impact of attacks that exploit uncontrolled consumption weaknesses.
Timely maintenance support and spare parts enable rapid recovery from failures induced by uncontrolled resource consumption, shortening the impact window of denial-of-service attacks.