GoApplication · Golang
CVE-2022-27536
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 · uneditedCertificate.Verify in crypto/x509 in Go 1.18.x before 1.18.1 can be caused to panic on macOS when presented with certain malformed certificates. This allows a remote TLS server to cause a TLS client to panic.
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 panic (crash) vulnerability exists in Go 1.18.x's crypto/x509 Certificate.Verify function on macOS. When a remote TLS server presents certain malformed certificates, the TLS client will panic instead of gracefully handling the error, causing denial of service.
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.18.0, < 1.18.1CVSS 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` and note the version number (e.g., go1.18.0)Affected if Version is greater than or equal to 1.18.0 and less than 1.18.1 (e.g., 1.18.0)
-
Verify the operating systemRun `uname -s` or check system info - this vulnerability only affects macOSAffected if Operating system is macOS (Darwin)
-
Confirm application uses crypto/x509 for certificate verificationInspect the application source code for `crypto/x509` package imports and usage of the `Verify` method on Certificate objects, or examine compiled binary with `strings` or dependency analysis toolsAffected if The application imports crypto/x509 and calls Certificate.Verify (or higher-level TLS functions that use it internally)
-
Identify TLS client usage on macOSReview application logs or network connections to determine if the application acts as a TLS client connecting to remote servers on macOSAffected if Application makes outbound TLS connections on macOS and uses the affected Go version
You are affected if running Go 1.18.0 on macOS with an application that performs TLS certificate verification using the crypto/x509 package.
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.18.1
Upgrade to Go 1.18.1 or later. Any application or service running Go 1.18.x on macOS that performs TLS certificate verification is affected and should be updated.
Go 1.18.1 or later (recommended: latest stable 1.18.x or 1.19+ release)
- Check the current Go version by running: go version
- Download Go 1.18.1 or later from the official Go website (https://go.dev/dl/)
- Install the new Go version following the official installation instructions for your operating system
- Verify the upgrade was successful by running: go version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27536 — 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-27536 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