GoApplication · Golang
CVE-2022-24675
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 · uneditedencoding/pem in Go before 1.17.9 and 1.18.x before 1.18.1 has a Decode stack overflow via a large amount of PEM data.
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 Go standard library's encoding/pem package contains a stack overflow vulnerability in its Decode function when processing a large amount of PEM-encoded data, allowing remote attackers to cause a denial of service via crafted input.
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.9>= 1.18.0, < 1.18.1
FedoraOperating system
= 34= 35= 36all 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 installed Go versionRun 'go version' in a terminal to see the installed Go versionAffected if The version shown is less than 1.17.9, or is 1.18.0 or 1.18.1 (for example, 'go1.18' or 'go1.18.0')
-
Verify Fedora OS versionRun 'cat /etc/fedora-release' or 'rpm -q fedora-release' to determine the Fedora versionAffected if The output shows version 34, 35, or 36 and Go is installed from system packages
-
Check for NetApp Kubernetes Monitoring OperatorLook for the product in the list of installed software or check running containers/processes for 'kubernetes-monitoring-operator' or 'kmo'Affected if The NetApp Kubernetes Monitoring Operator is installed or running on the system
You are affected if you are running Go versions prior to 1.17.9 or between 1.18.0 and 1.18.1, or if you are on Fedora 34/35/36 with system Go, or if the NetApp Kubernetes Monitoring Operator is present on any version.
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.91.18.1
Upgrade Go to version 1.17.9 or later, or 1.18.1 or later, to patch the encoding/pem stack overflow vulnerability.
Go 1.17.9+, Go 1.18.1+, or latest stable Go (1.19.x/1.20.x)
- 1. Identify the current Go version by running: go version
- 2. If running Go < 1.17.9 or Go 1.18.0, download and install the fixed version from https://go.dev/dl/
- 3. For Go 1.17.x users: upgrade to Go 1.17.9 or later (recommended: Go 1.17.13 or latest 1.17.x)
- 4. For Go 1.18.0 users: upgrade to Go 1.18.1 or later (recommended: Go 1.18.10 or latest 1.18.x, or migrate to Go 1.19+/1.20+)
- 5. Verify the upgrade was successful by running: go version
- 6. Rebuild any applications that use the encoding/pem package to ensure they use the patched Go runtime
- 7. For Kubernetes Monitoring Operator: rebuild/redeploy with the updated Go runtime
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
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24675 — 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-24675 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