GoApplication · Golang
CVE-2022-28131
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 · uneditedUncontrolled recursion in Decoder.Skip in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a deeply nested XML document.
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 confidenceThis is a stack exhaustion vulnerability in Go's standard library encoding/xml package. The Decoder.Skip function lacks proper recursion depth limits, allowing attackers to cause a panic (denial of service) by providing a deeply nested XML document that exhausts the call stack.
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.17.12>= 1.18.0, < 1.18.4
FedoraOperating system
= 35all 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.
-
Check the installed Go versionRun 'go version' in the terminal or check /usr/local/go/VERSION file. Alternatively, in a Go program, import 'runtime' and print runtime.Version()Affected if The version is earlier than 1.17.12, or at least 1.18.0 but earlier than 1.18.4
-
Identify if the application uses encoding/xmlSearch codebase for 'import "encoding/xml"' statements and usage of xml.DecoderAffected if The application imports and uses the encoding/xml package to parse XML data
-
Check if XML input sources are untrusted or externalReview code that creates xml.NewDecoder from io.Reader sources such as HTTP request bodies, file uploads, or network connectionsAffected if The application parses XML from untrusted sources like HTTP requests, user uploads, or external APIs without strict depth limits
-
Verify if Decoder.Skip or recursive parsing is usedSearch for calls to xml.Decoder.Skip method or custom recursive XML parsing functions that process nested elementsAffected if The application uses Decoder.Skip or any recursive XML element parsing without explicit depth limiting controls
-
Confirm operating system if running Fedora 35Check /etc/fedora-release or run 'cat /etc/os-release' to verify the OS versionAffected if Running Fedoraproject Fedora version 35 with affected Go packages installed
You are affected if your Go version is below 1.17.12 or between 1.18.0 and 1.18.4, AND your application uses encoding/xml to parse untrusted or deeply nested XML documents.
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.17.121.18.4
Upgrade the Go runtime to version 1.17.12, 1.18.4, or later. This is a standard library fix requiring no application code changes.
Go 1.17.12, Go 1.18.4, or later (prefer latest stable 1.18.x or 1.19+)
- Identify the current Go version installed by running: go version
- If using Go directly, download and install Go 1.18.4 or later (or Go 1.17.12 or later in the 1.17 branch) from https://go.dev/dl/
- For Fedora 35 systems, run: sudo dnf update golang
- For Cloud Insights Telegraf, upgrade the underlying Go runtime to the fixed version, then rebuild/redeploy Telegraf with: go build -mod=mod ./...
- Verify the fix by running: go version and confirm it shows 1.17.12+, 1.18.4+, or later
- Test that XML parsing with deeply nested documents no longer causes stack exhaustion or panic
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28131 — 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-28131 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