GoApplication · Golang
CVE-2022-23773
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 · uneditedcmd/go in Go before 1.16.14 and 1.17.x before 1.17.7 can misinterpret branch names that falsely appear to be version tags. This can lead to incorrect access control if an actor is supposed to be able to create branches but not tags.
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 confidencecmd/go in Go versions before 1.16.14 and 1.17.x before 1.17.7 misinterprets branch names that appear to be version tags, allowing actors with branch creation permissions to potentially bypass access controls intended to prevent tag creation.
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.14>= 1.17.0, < 1.17.7all versionsall versionsall 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 a terminal or check /usr/local/go/VERSION (if installed via official installer)Affected if The version is below 1.16.14, or between 1.17.0 and 1.17.6 inclusive
-
Check Go version in containerized environmentsInspect the base image or runtime: 'docker run golang:version go version' or check the image manifest for the Go version it shipsAffected if The container image uses a Go version below 1.16.14 or between 1.17.0 and 1.17.6
-
Identify Go bundled in third-party productsLocate the Go binary within the product's installation directory (common paths: /opt/vendor/bin, /usr/bin, or within the product's lib folder) and run 'go version' on that binaryAffected if The bundled Go version is below 1.16.14 or between 1.17.0 and 1.17.6
-
Check build pipeline Go versionReview CI/CD configuration files (such as .travis.yml, .gitlab-ci.yml, or GitHub Actions workflows) that specify the Go version for buildsAffected if The configured Go version is below 1.16.14 or between 1.17.0 and 1.17.6
You are affected if any Go installation in your environment (direct or bundled) has a version lower than 1.16.14 or falls within the 1.17.0 through 1.17.6 range.
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.141.17.7
Upgrade Go to version 1.16.14, 1.17.7, or later. Audit repository access control policies to ensure branch creation cannot be leveraged as a tag creation bypass.
Go 1.16.14+ or Go 1.17.7+ (or latest stable 1.18+/1.19+)
- Upgrade Go to version 1.16.14 or later (if using the 1.16.x line)
- Upgrade Go to version 1.17.7 or later (if using the 1.17.x line)
- For products that bundle Go (Beegfs Csi Driver, Cloud Insights Telegraf Agent, Kubernetes Monitoring Operator, Storagegrid), obtain and apply product-specific updates that incorporate the fixed Go version
- Verify the Go version after upgrade using: go version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23773 — 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-2022-23773 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