GoApplication · Golang
CVE-2020-7919
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 · uneditedGo before 1.12.16 and 1.13.x before 1.13.7 (and the crypto/cryptobyte package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients (resulting in a panic) via a malformed X.509 certificate.
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 confidenceGo's crypto/cryptobyte and crypto/x509 packages fail to properly validate malformed X.509 certificates, allowing remote attackers to cause a panic (crash) in affected Go clients by presenting a specially crafted certificate during TLS handshake.
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.12, < 1.12.6>= 1.13, < 1.13.7
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 31all 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' to see the Go compiler versionAffected if Version is 1.12.0 through 1.12.5, or 1.13.0 through 1.13.6 (falls within >=1.12 <1.12.6 or >=1.13 <1.13.7)
-
Check Go package version on Debian 10Run 'dpkg -l | grep golang' or 'apt show golang' to see the installed Go package versionAffected if The installed golang package version is less than 1.12.6 or less than 1.13.7
-
Check Go package version on Fedora 31Run 'rpm -qa | grep golang' to see the installed Go package versionAffected if The installed golang package version is less than 1.12.6 or less than 1.13.7
-
Identify Go binaries that perform TLS connectionsSearch for Go-compiled binaries that use crypto/tls or crypto/x509 by running 'go version -m <binary>' on suspected binaries, or check application logs for TLS activityAffected if The binary is compiled with a vulnerable Go version and accepts incoming TLS connections or makes outbound TLS connections to untrusted servers
You are affected if your system runs Go versions 1.12.x before 1.12.6 or 1.13.x before 1.13.7, or uses Go binaries compiled with those versions and processes X.509 certificates during TLS handshakes.
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.
From vendor data1.12.61.13.7
Upgrade Go to version 1.12.16 or 1.13.7 or later, or update the crypto/cryptobyte package to version 0.0.0-20200124225646-8b5121be2f68 or higher.
Fix this in Go
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7919 — 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-2020-7919 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