GoApplication · Golang
CVE-2021-3115
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.14.14 and 1.15.x before 1.15.7 on Windows is vulnerable to Command Injection and remote code execution when using the "go get" command to fetch modules that make use of cgo (for example, cgo can execute a gcc program from an untrusted download).
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 before 1.14.14 and 1.15.x before 1.15.7 on Windows contains a command injection vulnerability in the module fetching mechanism. When using 'go get' to retrieve modules containing cgo code, the cgo feature can execute gcc programs from untrusted downloads, allowing remote code execution.
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.14>= 1.15, < 1.15.7
FedoraOperating system
= 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.
-
Verify the operating system is WindowsRun 'uname -s' or check system properties. This vulnerability only affects Windows systems.Affected if The system is running Windows and the Go version is below 1.14.14 or between 1.15.0 and 1.15.6 inclusive.
-
Check installed Go versionRun 'go version' to retrieve the Go toolchain version.Affected if The reported version is less than 1.14.14, or greater than or equal to 1.15.0 but less than 1.15.7.
-
Confirm cgo is enabled and modules are in useRun 'go env CGO_ENABLED' and 'go env GO111MODULE'. The vulnerability requires cgo to be enabled (CGO_ENABLED=1) and module mode to be active.Affected if CGO_ENABLED is set to 1 and modules are being used (GO111MODULE may be on or auto).
-
Check if NetApp Cloud Insights Telegraf Agent is installedInspect installed software or check for the Telegraf binary location (commonly in /opt/telegraf or similar). NetApp bundles Go in this agent.Affected if Cloud Insights Telegraf Agent is installed on Windows (all versions are affected).
-
Check if NetApp StorageGRID is in useVerify presence of NetApp StorageGRID infrastructure. This product bundles a vulnerable Go version.Affected if StorageGRID is deployed on Windows (all versions are affected).
A user is affected if they are running Windows with Go versions below 1.14.14 or between 1.15.0 and 1.15.6, especially when using 'go get' with cgo-enabled modules, or if they have NetApp products (Cloud Insights Telegraf Agent or StorageGRID) installed on Windows.
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.141.15.7
Upgrade Go to version 1.14.14 or later, or 1.15.7 or later on all Windows systems. Avoid using 'go get' to fetch modules from untrusted sources.
Fix this in Go
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3115 — 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-2021-3115 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