GoApplication · Golang
CVE-2022-28327
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 · uneditedThe generic P-256 feature in crypto/elliptic in Go before 1.17.9 and 1.18.x before 1.18.1 allows a panic via long scalar input.
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 confidenceA denial-of-service vulnerability exists in Go's crypto/elliptic package P-256 implementation where processing an excessively long scalar input triggers a panic, causing the application to crash. The vulnerability is exploitable remotely without authentication by providing specially crafted input to elliptic curve operations.
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= 36= 7.0= 8.0CVSS 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' to see the Go compiler version, or check the Go installation directory for the version fileAffected if The version is below 1.17.9, or at 1.18.0 (versions 1.18.1 and later are patched)
-
Identify applications using crypto/elliptic packageSearch codebase for imports of 'crypto/elliptic' and usage of functions such as P256, GenerateKey, or ScalarMult involving P-256 curvesAffected if The application imports and uses the crypto/elliptic package with P-256 curves
-
Check if P-256 curve operations process external inputReview code paths where elliptic.ScalarMult, elliptic.ScalarBaseMult, or similar functions receive user-supplied or network-received scalar valuesAffected if External scalar input flows to P-256 elliptic curve functions without length validation
-
Verify application exposure to network inputExamine whether the application accepts remote connections or parsed data that could provide scalar values to elliptic curve functions (e.g., TLS handshake handlers, cryptographic protocol implementations)Affected if The application exposes elliptic curve operations to untrusted external input
You are affected if running a Go version before 1.17.9 or at 1.18.0 AND your application uses P-256 curve operations from crypto/elliptic package with external input.
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, then rebuild and redeploy all affected applications that use the crypto/elliptic package with P-256 curves.
Go 1.17.9 or Go 1.18.1 (or later stable release)
- Check the current Go version by running 'go version'
- Download Go 1.17.9 or Go 1.18.1 (or later stable release) from the official Go downloads page
- Install the new Go version following standard installation procedures for your operating system
- Verify the upgrade was successful by running 'go version' and confirming it shows 1.17.9+ or 1.18.1+
- Rebuild any applications that use the crypto/elliptic package to ensure they use the patched library
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28327 — 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-28327 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