GoApplication · Golang
CVE-2022-27664
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a denial-of-service vulnerability in Go's net/http package affecting HTTP/2 connections. When an HTTP/2 connection shutdown is preempted by a fatal error, the connection can hang indefinitely, allowing attackers to exhaust server resources by triggering this condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GoApplication
< 1.18.6= 1.19.0
FedoraOperating system
= 36= 37CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Go versionRun 'go version' to get the Go runtime versionAffected if Version is less than 1.18.6 or equal to 1.19.0
-
Check if HTTP/2 is enabled in the applicationInspect application code or configuration for use of http2 library or HTTP/2 enablement in net/http server (e.g., check for 'http2.ConfigureServer' or 'h2c' upgrade configurations)Affected if HTTP/2 is enabled and the Go version is vulnerable
-
Verify the Go installation path and package versionCheck the Go toolchain version file: 'go version' output, or examine /usr/local/go/VERSION if installed from tarballAffected if The installed Go version matches the affected ranges (< 1.18.6 or = 1.19.0)
-
Check Fedora system version (if applicable)Run 'cat /etc/fedora-release' or 'rpm -q fedora-release' to identify the Fedora versionAffected if Running Fedora 36 or 37 with default Go packages
You are affected if your Go version is less than 1.18.6 or equals 1.19.0 (or Fedora 36/37 with default Go), and your application or service uses HTTP/2 connections.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.18.6
Upgrade Go to version 1.18.6 or 1.19.1 or later, which contains the fix for this HTTP/2 connection hang issue.
Go 1.18.6 or Go 1.19.1+
- Upgrade Go to version 1.18.6 or later for the 1.18 branch
- Alternatively, upgrade Go to version 1.19.1 or later for the 1.19 branch
- Verify the upgrade by running 'go version' to confirm the installed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data