dbcve.org
GoApplication · Golang

CVE-2022-23806

CRITICAL · 9.1 CVSS v3.1 Published 2022-02-11
Fix available
A fix is available. Upgrade to 1.16.14 / 1.17.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Curve.IsOnCurve in crypto/elliptic in Go before 1.16.14 and 1.17.x before 1.17.7 can incorrectly return true in situations with a big.Int value that is not a valid field element.

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 Curve.IsOnCurve function in Go's crypto/elliptic package incorrectly validates whether a point lies on an elliptic curve. The function can return true for big.Int values that are not valid field elements, potentially allowing attackers to bypass cryptographic validation checks. This affects all uses of elliptic curve cryptography where this validation function is consulted.

MitigationUpgrade Go to version 1.16.14 or 1.17.7 or later. Review any code paths that depend on Curve.IsOnCurve for proper security guarantees.

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.14>= 1.17.0, < 1.17.7
Debian LinuxOperating system
Affected:= 9.0
Beegfs Csi DriverApplication
Affected:all versions
Cloud Insights Telegraf AgentApplication
Affected:all versions
Kubernetes Monitoring OperatorApplication
Affected:all versions
StoragegridApplication
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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check Go version installed
    Run 'go version' to see the installed Go version
    Affected if Version is less than 1.16.14, or greater than or equal to 1.17.0 but less than 1.17.7
  2. Verify use of crypto/elliptic package
    Search codebase for 'import crypto/elliptic' or 'crypto/elliptic' statements
    Affected if The crypto/elliptic package is imported and used in the application
  3. Identify IsOnCurve function calls
    Search code for calls to IsOnCurve method on Curve objects
    Affected if Code calls Curve.IsOnCurve() to validate elliptic curve points
  4. Check if application performs EC point operations
    Review code for elliptic curve point parsing, decompression, or deserialization from external input
    Affected if Application processes EC points from untrusted sources without additional validation
  5. For NetApp products, identify the Go runtime version
    Check product documentation or runtime for the bundled Go version
    Affected if NetApp product ships with vulnerable Go version (all versions listed are affected if using vulnerable Go)
  6. On Debian 9.0 systems, check golang package
    Run 'dpkg -l | grep golang' to see installed Go packages
    Affected if Running Debian 9.0 with Go packages from that release

You are affected if your Go version is below 1.16.14 or between 1.17.0 and 1.17.7, and your code uses crypto/elliptic.IsOnCurve() to validate points from external sources.

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.14 / 1.17.7 or later
Fixed in 1.16.141.17.7
Interim mitigation

Upgrade Go to version 1.16.14 or 1.17.7 or later. Review any code paths that depend on Curve.IsOnCurve for proper security guarantees.

Recommended fix High confidence

Go 1.16.14+ or Go 1.17.7+ (or latest stable 1.17.x/1.18+)

  1. Upgrade Go to version 1.16.14 or later, OR upgrade to version 1.17.7 or later
  2. If using a Go-based product (Beegfs Csi Driver, Cloud Insights Telegraf Agent, Kubernetes Monitoring Operator, Storagegrid), rebuild/reinstall the product with the fixed Go version to incorporate the crypto/elliptic patch
  3. For Debian Linux 9.0, apply the Debian security update that patches the Go package to a fixed version
  4. Verify the fix by testing that Curve.IsOnCurve correctly rejects invalid field elements
Caveat Go 1.17 introduced some language changes; however, this security fix is critical and should be applied. Consider also moving to Go 1.18+ for additional stability if compatibility allows.

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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