Skip to content

quic-go vulnerable to pointer dereference that can lead to panic

High severity GitHub Reviewed Published Oct 27, 2023 in quic-go/quic-go • Updated Nov 9, 2023

Package

gomod github.com/quic-go/quic-go (Go)

Affected versions

>= 0.37.0, < 0.37.3

Patched versions

0.37.3

Description

quic-go is an implementation of the QUIC transport protocol in Go. By serializing an ACK frame after the CRYTPO that allows a node to complete the handshake, a remote node could trigger a nil pointer dereference (leading to a panic) when the node attempted to drop the Handshake packet number space.

Impact

An attacker can bring down a quic-go node with very minimal effort. Completing the QUIC handshake only requires sending and receiving a few packets.

Patches

v0.37.3 contains a patch. Versions before v0.37.0 are not affected.

References

@marten-seemann marten-seemann published to quic-go/quic-go Oct 27, 2023
Published to the GitHub Advisory Database Oct 30, 2023
Reviewed Oct 30, 2023
Published by the National Vulnerability Database Oct 31, 2023
Last updated Nov 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.053%
(22nd percentile)

Weaknesses

CVE ID

CVE-2023-46239

GHSA ID

GHSA-3q6m-v84f-6p9h

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.