dbcve.org
GoApplication · Golang

CVE-2022-24921

HIGH · 7.5 CVSS v3.1 Published 2022-03-05
Fix available
A fix is available. Upgrade to 1.16.15 / 1.17.8 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
regexp.Compile in Go before 1.16.15 and 1.17.x before 1.17.8 allows stack exhaustion via a deeply nested expression.

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

The regexp.Compile function in Go versions prior to 1.16.15 and 1.17.x prior to 1.17.8 contains a stack exhaustion vulnerability. Attackers can trigger excessive recursive calls during regex compilation by providing deeply nested expressions, potentially causing denial of service through stack overflow.

MitigationUpgrade Go to version 1.16.15, 1.17.8, or later. If immediate upgrading is not feasible, ensure that untrusted regular expression patterns are not compiled without validation or resource limits.

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.16.15>= 1.17, < 1.17.8
Debian LinuxOperating system
Affected:= 9.0
Astra TridentApplication
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. Identify installed Go version
    Run 'go version' in your terminal or check the Go binary path. On Linux systems, you may also check the system package manager (e.g., 'dpkg -l | grep golang' on Debian-based systems).
    Affected if The version shown is earlier than 1.16.15, or is 1.17.x earlier than 1.17.8 (for example, 1.17.0 through 1.17.7).
  2. Check if running on Debian 9.0
    Run 'cat /etc/debian_version' or 'lsb_release -a' to identify the Debian release version.
    Affected if The system is Debian Linux version 9.0 and the Go package installed is the system-provided version (verify with 'dpkg -l golang').
  3. Identify if NetApp Astra Trident is deployed
    Check for installed Trident components by running 'tridentctl version' or looking for Trident pods in Kubernetes (e.g., 'kubectl get pods -n trident' or 'kubectl get all -n trident').
    Affected if Astra Trident is installed and running, regardless of version.
  4. Verify if application code uses regexp.Compile with external input
    Search your codebase for uses of regexp.Compile, regexp.CompilePOSIX, or similar functions that process user-supplied or externally sourced regex patterns. Review the data flow to confirm whether untrusted input reaches these functions.
    Affected if Your application compiles regex patterns from sources you do not fully control (user input, network data, external configuration files).

You are affected if your Go version is below 1.16.15 or between 1.17.0 and 1.17.7 inclusive, or if you run Debian 9.0 with system Go, or if you use Astra Trident, AND your code compiles regex patterns from potentially untrusted input.

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 1.16.15 / 1.17.8 or later
Fixed in 1.16.151.17.8
Interim mitigation

Upgrade Go to version 1.16.15, 1.17.8, or later. If immediate upgrading is not feasible, ensure that untrusted regular expression patterns are not compiled without validation or resource limits.

Recommended fix High confidence

Go 1.16.15+, 1.17.8+, or latest stable 1.x (recommended)

  1. 1. Identify the current Go version by running: go version
  2. 2. For systems with Go < 1.16.15: Upgrade to Go 1.16.15 or later (preferably latest 1.16.x stable)
  3. 3. For systems with Go >= 1.17.0 and < 1.17.8: Upgrade to Go 1.17.8 or later (preferably latest 1.17.x or 1.x stable)
  4. 4. For Debian 9.0 systems: Update the Go package via apt-get update && apt-get upgrade golang-go, or upgrade to a newer Debian release
  5. 5. For Astra Trident: Rebuild/reinstall using a fixed Go version (upgrade Trident to latest version which includes the fix)
  6. 6. Verify the fix by running: go version (should show >= 1.16.15 or >= 1.17.8)
  7. 7. Test that regexp.Compile works correctly with your regular expressions
Caveat Go point releases rarely introduce breaking changes, but test your regex patterns after upgrade to ensure expected behavior

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

Fix this in Go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24921 — 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-2022-24921 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