What is the vulnerability ID of this vulnerability?

The vulnerability ID of this vulnerability is CVE-2022-30591.

What is the severity of CVE-2022-30591?

CVE-2022-30591 has a severity rating of 7.5 (High).

How does quic-go through 0.27.0 allow remote attackers to cause a denial of service?

quic-go through 0.27.0 allows remote attackers to cause a denial of service by sending incomplete QUIC or HTTP/3 requests, which leads to CPU consumption.

How can I fix CVE-2022-30591?

To address CVE-2022-30591, consider updating to a version of quic-go beyond 0.27.0 that resolves the issue.

Is there any reference available for this vulnerability?

Yes, you can find more information about CVE-2022-30591 at the following link: [Github - mtu_discoverer.go](https://github.com/lucas-clemente/quic-go/blob/84e03e59760ceee37359688871bb0688fcc4e98f/mtu_discoverer.go).

Vulnerability/
CVE-2022-30591

high

7.5

CWE

400

6/7/2022

3/8/2024

CVE-2022-30591

First published: Wed Jul 06 2022(Updated: )

** DISPUTED ** 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 probe timer. NOTE: the vendor's position is that this behavior should not be listed as a vulnerability on the CVE List.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
quic-go	<=0.27.0

Never miss a vulnerability like this again

Reference Links

https://github.com/lucas-clemente/quic-go/blob/84e03e59760ceee37359688871bb0688fcc4e98f/mtu_discoverer.go

Frequently Asked Questions

What is the vulnerability ID of this vulnerability?
The vulnerability ID of this vulnerability is CVE-2022-30591.
What is the severity of CVE-2022-30591?
CVE-2022-30591 has a severity rating of 7.5 (High).
How does quic-go through 0.27.0 allow remote attackers to cause a denial of service?
quic-go through 0.27.0 allows remote attackers to cause a denial of service by sending incomplete QUIC or HTTP/3 requests, which leads to CPU consumption.
How can I fix CVE-2022-30591?
To address CVE-2022-30591, consider updating to a version of quic-go beyond 0.27.0 that resolves the issue.
Is there any reference available for this vulnerability?
Yes, you can find more information about CVE-2022-30591 at the following link: [Github - mtu_discoverer.go](https://github.com/lucas-clemente/quic-go/blob/84e03e59760ceee37359688871bb0688fcc4e98f/mtu_discoverer.go).

agent/type
agent/severity
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/status
agent/description
collector/mitre-cve
source/MITRE
agent/first-publish-date
agent/event
agent/last-modified-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
status/disputed
vendor/quic-go project
canonical/quic-go
version/quic-go/0.27.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.