GoApplication · Golang
CVE-2021-39293
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 · uneditedIn archive/zip in Go before 1.16.8 and 1.17.x before 1.17.1, a crafted archive header (falsely designating that many files are present) can cause a NewReader or OpenReader panic. NOTE: this issue exists because of an incomplete fix for CVE-2021-33196.
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 crafted ZIP archive with falsified header information (claiming many files are present) can cause a panic in Go's archive/zip NewReader or OpenReader functions. This is an incomplete fix for CVE-2021-33196.
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.16.8>= 1.17.0, < 1.17.1all 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' in the terminal or check the Go binary path with 'which go' and then run the version commandAffected if The version is less than 1.16.8, or greater than or equal to 1.17.0 but less than 1.17.1
-
Check for Netapp Cloud Insights Telegraf installationLook for the telegraf binary or service, commonly in /usr/bin/telegraf, /opt/telegraf, or check running services with 'systemctl list-units | grep telegraf' or 'ps aux | grep telegraf'Affected if Netapp Cloud Insights Telegraf is installed and running (all versions are affected)
-
Identify Go-based applications that process ZIP archivesReview application code or dependencies for usage of archive/zip NewReader or OpenReader functions, or examine any custom Go binaries that handle ZIP file inputAffected if Any Go application built with a vulnerable Go version processes ZIP archives using the affected functions
You are affected if you run Go versions below 1.16.8 or between 1.17.0 and 1.17.1, or if you have Netapp Cloud Insights Telegraf installed, and any of these handle ZIP archives from untrusted sources.
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.16.81.17.1
Upgrade Go to version 1.16.8 or 1.17.1 or later to obtain the patched standard library that properly validates archive headers.
Go 1.16.8 or Go 1.17.1 (or later stable release)
- Check current Go version by running: go version
- Download Go 1.16.8 or Go 1.17.1 (or later stable version) from https://go.dev/dl/
- Install the new Go version following the standard installation process for your operating system
- Verify the upgrade was successful by running: go version
- Rebuild any applications that use the archive/zip package to ensure they use the patched Go runtime
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39293 — 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-39293 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