GoApplication · Golang
CVE-2020-28366
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 · uneditedCode injection in the go command with cgo before Go 1.14.12 and Go 1.15.5 allows arbitrary code execution at build time via a malicious unquoted symbol name in a linked object file.
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 confidenceCode injection vulnerability in the Go toolchain's cgo component allows arbitrary code execution during build time. Attackers can exploit unquoted symbol names in linked object files to inject and execute malicious code when the Go build process processes these files. This affects Go versions prior to 1.14.12 and 1.15.5.
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.14.12>= 1.15, < 1.15.5
FedoraOperating system
= 32= 33all versionsall 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Go versionRun 'go version' to identify the Go toolchain versionAffected if Version is before 1.14.12, or is 1.15.0 through 1.15.4
-
Verify if cgo is enabledCheck for CGO_ENABLED=1 in environment or search for '//go:cgo' directives in source filesAffected if cgo is enabled and used in the build process
-
Inspect CGO_LDFLAGS environment variableRun 'echo $CGO_LDFLAGS' or check build scripts for CGO_LDFLAGS definitionsAffected if CGO_LDFLAGS contains linked object files with unquoted symbol names
-
Check for Fedora OS version (if applicable)Run 'cat /etc/fedora-release' or 'hostnamectl'Affected if Running Fedora 32 or Fedora 33 with vulnerable Go packages
-
Check for NetApp products (if applicable)Identify installed NetApp Cloud Insights Telegraf Agent or Trident installationsAffected if Either NetApp product is present (both listed as affected for all versions)
You are affected if your Go version is < 1.14.12 or between 1.15.0-1.15.4 AND you use cgo in your builds with untrusted or unquoted object files in CGO_LDFLAGS.
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.14.121.15.5
Upgrade Go toolchain to version 1.14.12+, 1.15.5+, or preferably 1.16+ as the primary remediation. Additionally, audit all cgo CGO_LDFLAGS and linked object files to ensure only trusted code is included in builds.
Fix this in Go
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28366 — 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-28366 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