All reports
Medium

quic-go's path validation mechanism can be exploited to cause denial of service

Affected versions

Version ranges need review.

Affected versions
<0.37.7 || >=0.38.0 <0.38.2 || >=0.39.0 <0.39.4 || >=0.40.0 <0.40.1
Fixed version
0.37.7 · 0.38.2 · 0.39.4 · 0.40.1
Affected versions
>= 0.39.0, < 0.39.4
Fixed version
0.39.4
Affected versions
= 0.40.0
Fixed version
0.40.1
Affected versions
>= 0.38.0, < 0.38.2
Fixed version
0.38.2
Affected versions
< 0.37.7
Fixed version
0.37.7
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-49295

Probability of exploitation in the next 30 days: 1.20%

FIRST EPSS · 2026-11-20

Description

An attacker can cause its peer to run out of memory sending a large number of PATH_CHALLENGE frames. The receiver is supposed to respond to each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prevent the receiver from sending out (the vast majority of) these PATH_RESPONSE frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.

I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2023-12-18-exploiting-quics-path-validation/

There's no way to mitigate this attack, please update quic-go to a version that contains the fix.

Links

Credits

  • marten-seemann