GoApplication · Golang
CVE-2022-23772
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 · uneditedRat.SetString in math/big in Go before 1.16.14 and 1.17.x before 1.17.7 has an overflow that can lead to Uncontrolled Memory Consumption.
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 confidenceThe Rat.SetString function in Go's math/big package contains an integer overflow vulnerability that allows an attacker to cause uncontrolled memory consumption by providing specially crafted input strings. When parsing rational numbers, the overflow can cause the memory allocation to fail silently or allocate far more memory than intended, potentially leading to denial of service.
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.16.14>= 1.17.0, < 1.17.7
Debian LinuxOperating system
= 9.0all versionsall versionsall versionsall versionsCVSS 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.
-
Identify installed Go versionRun 'go version' from command line or check /usr/local/go/VERSION file if installed from sourceAffected if Version is earlier than 1.16.14, or between 1.17.0 and 1.17.7 inclusive, indicating the vulnerable versions are in use
-
Check for Go applications using math/big.Rat.SetStringSearch application source code or binaries for usage of 'math/big' package and 'Rat' type with 'SetString' method, especially with input from untrusted sources such as user input, API requests, or network dataAffected if Applications process rational number strings from untrusted input through the vulnerable function
-
Identify vulnerable NetApp productsCheck installed packages or containers for: beegfs-csi-driver, cloud-insights-telegraf-agent, kubernetes-monitoring-operator, or storagegrid productsAffected if Any of these NetApp products are running, as all versions are affected per vendor advisory
-
Check Debian system Go packageOn Debian 9.0 systems, run 'dpkg -l | grep golang' or check apt policy golang-go to see installed versionAffected if Running Debian 9.0 with Go packages installed, as this specific version is listed as affected
You are affected if you run any Go version prior to 1.16.14 or between 1.17.0-1.17.7, or have installed the vulnerable NetApp products, AND your applications use math/big.Rat.SetString with untrusted input that could trigger the memory exhaustion.
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.16.141.17.7
Upgrade Go runtime to version 1.16.14, 1.17.7, or later. Audit all applications and services that use math/big.Rat.SetString with untrusted input to ensure they handle memory allocation errors properly.
Go 1.16.14 or later, or Go 1.17.7 or later (recommended: latest stable 1.17.x or 1.18+)
- 1. Identify the current Go version installed by running: go version
- 2. If running Go < 1.16.14 or >= 1.17.0 but < 1.17.7, plan for an upgrade
- 3. Download the appropriate fixed Go release from https://go.dev/dl/ (1.16.14 or 1.17.7 or later)
- 4. Install the new Go version following standard installation procedures for your OS
- 5. Verify the upgrade was successful by running: go version
- 6. Rebuild any applications that use the math/big package to ensure they use the fixed runtime
- 7. Test that Rat.SetString functionality works correctly with your application inputs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23772 — 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-23772 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