GoApplication · Golang
CVE-2021-41772
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.16.10 and 1.17.x before 1.17.3 allows an archive/zip Reader.Open panic via a crafted ZIP archive containing an invalid name or an empty filename field.
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 archive/zip package Reader.Open function contains a vulnerability where processing a specially crafted ZIP archive with an invalid or empty filename field triggers a panic, causing denial of service. An attacker can exploit this by enticing a user or service to process a malicious ZIP file.
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.10>= 1.17.0, < 1.17.3
FedoraOperating system
= 34= 35all 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.
-
Identify installed Go versionRun 'go version' in a terminal to see the Go compiler version. Alternatively, check via package manager: 'rpm -q golang' (RHEL/Fedora) or 'dpkg -l | grep golang' (Debian).Affected if The version is below 1.16.10, or is 1.17.0, 1.17.1, or 1.17.2.
-
Verify Go module usage of archive/zipSearch your codebase for imports of 'archive/zip' and calls to Reader.Open or NewReader. Run: grep -r 'archive/zip' your-project/Affected if Your code imports and uses archive/zip to process ZIP files.
-
Check if ZIP input is from untrusted sourcesAudit where ZIP files are opened in your application. Look for user uploads, external API inputs, or network-received archives being passed to zip.Reader.Open.Affected if Your application processes ZIP archives from user uploads, external APIs, or other untrusted sources without validating filename fields.
-
Confirm OS version on Fedora systemsRun 'cat /etc/fedora-release' or 'rpm -q fedora-release' to identify the Fedora version.Affected if Running Fedora 34 or Fedora 35 with the vulnerable Go package installed.
You are affected if you run Go versions below 1.16.10 or between 1.17.0 and 1.17.2, AND your application uses the archive/zip package to process ZIP files from any source.
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.101.17.3
Upgrade Go to version 1.16.10 or 1.17.3 or later. If immediate patching is not possible, avoid processing ZIP archives from untrusted sources and implement input validation to reject archives with empty or malformed filename fields.
Go >= 1.16.10 or Go >= 1.17.3 (any stable release after 1.17.3)
- Check current Go version by running: go version
- Upgrade Go to version 1.16.10, 1.17.3, or later using your package manager or by downloading from https://golang.org/dl/
- If using a package manager (e.g., apt, yum, brew), run the appropriate update command for your system
- Verify the upgrade was successful by running: go version
- Ensure the reported version is >= 1.16.10 or >= 1.17.3
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
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41772 — 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-41772 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