GoApplication · Golang
CVE-2017-1000097
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 · uneditedOn Darwin, user's trust preferences for root certificates were not honored. If the user had a root certificate loaded in their Keychain that was explicitly not trusted, a Go program would still verify a connection using that root certificate.
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 · moderate confidenceOn Darwin/macOS, Go's crypto/tls package did not respect user-defined trust settings in the macOS Keychain. When a root certificate was explicitly marked as untrusted by the user in their Keychain, Go programs would still use that certificate to verify TLS connections, bypassing user-level certificate trust preferences.
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.6.4>= 1.7, < 1.7.4CVSS 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 Go versionRun 'go version' in terminal and compare the version number to the affected ranges: < 1.6.4 or >= 1.7.0 to < 1.7.4Affected if The installed Go version falls within < 1.6.4 or >= 1.7.0 to < 1.7.4 on macOS
-
Confirm macOS/Darwin platformRun 'uname -s' and verify the output is 'Darwin', or check System Preferences > About for macOS versionAffected if The system is running macOS/Darwin; this vulnerability does not affect other platforms
-
Identify Go programs using TLS with default Keychain trustSearch Go codebase for uses of 'crypto/tls' package with default TLS configuration (Config rootCA field not set, or using tls.Config{} without custom RootCAs)Affected if The Go application uses crypto/tls without explicitly setting a custom CA bundle and relies on the system Keychain for certificate verification
-
Inspect Keychain for explicitly untrusted certificatesOpen Keychain Access app, select 'System Roots' or 'login' keychain, and look for certificates with a red X indicating 'Always Trust: Never' or explicitly untrusted statusAffected if There are certificates in the Keychain that the user has explicitly marked as untrusted, which Go would still accept for TLS verification
User is affected if running Go versions < 1.6.4 or >= 1.7.0 to < 1.7.4 on macOS with Go programs that use default TLS verification relying on the Keychain, and there are certificates explicitly marked as untrusted in the Keychain that should be rejected but would be accepted.
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.6.41.7.4
Upgrade to Go version 1.8.4 or later (or Go 1.9+) which contains the fix. Alternatively, remove untrusted certificates from the Keychain or use custom TLS configurations with explicit CA bundles.
Fix this in Go
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000097 — 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-2017-1000097 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