dbcve.org
GoApplication · Golang

CVE-2023-39325

HIGH · 7.5 CVSS v3.1 Published 2023-10-11
Fix available
A fix is available. Upgrade to 0.17.0 / 1.20.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

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 · high confidence

A malicious HTTP/2 client can rapidly create requests and immediately reset them before completion, allowing the attacker to spawn more concurrent handler goroutines than the http2.Server.MaxConcurrentStreams limit intended. This occurs because resetting an in-progress request frees the client to issue a new request while the previous handler still executes, bypassing the stream concurrency bound.

MitigationUpgrade Go to version 1.21.1 or later, or update golang.org/x/net/http2 to the version containing the fix. Consider tuning MaxConcurrentStreams if the default of 250 is insufficient for legitimate traffic patterns.

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
Affected:>= 1.20.0, < 1.20.10>= 1.21.0, < 1.21.3
Http2Application
Affected:< 0.17.0
FedoraOperating system
Affected:= 37= 38= 39
Astra TridentApplication
Affected:all versions
Astra Trident AutosupportApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Go version
    Run 'go version' to see the installed Go version number
    Affected if The version is >= 1.20.0 and < 1.20.10, OR >= 1.21.0 and < 1.21.3
  2. Check golang.org/x/net/http2 package version
    Run 'go list -m golang.org/x/net' or inspect the go.mod file for the http2 package version
    Affected if The golang.org/x/net version is less than 0.17.0
  3. Verify HTTP/2 server is in use
    Inspect application code or server configuration for http2.Server usage, or check if the application serves over HTTP/2 (check for h2 or h2c in protocol negotiation)
    Affected if HTTP/2 server is enabled and serving traffic
  4. Check MaxConcurrentStreams configuration
    Search source code for 'MaxConcurrentStreams' setting in http2.Server configuration, or inspect environment variables or config files that may set this value
    Affected if The application uses default MaxConcurrentStreams (250) or any value that could be overwhelmed by rapid request creation and reset cycles

The environment is affected if it runs Go versions 1.20.0-1.20.9 or 1.21.0-1.21.2, or golang.org/x/net/http2 below 0.17.0, AND has an HTTP/2 server exposed to untrusted clients.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.17.0 / 1.20.10 / 1.21.3 or later
Fixed in 0.17.01.20.101.21.3
Interim mitigation

Upgrade Go to version 1.21.1 or later, or update golang.org/x/net/http2 to the version containing the fix. Consider tuning MaxConcurrentStreams if the default of 250 is insufficient for legitimate traffic patterns.

Recommended fix High confidence

Go 1.20.10+/1.21.3+ or golang.org/x/net/http2 v0.17.0+

  1. Upgrade Go to version 1.20.10 or later, or version 1.21.3 or later
  2. If using golang.org/x/net/http2 directly, upgrade to version 0.17.0 or later
  3. For Fedora systems, apply security updates via: sudo dnf update --security
  4. For Astra Trident products, contact NetApp for vendor-supplied patches addressing this vulnerability in their affected releases

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39325 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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