CVE-2017-13832
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 · uneditedAn issue was discovered in certain Apple products. macOS before 10.13.1 is affected. The issue involves the "802.1X" component. It allows attackers to have an unspecified impact by leveraging TLS 1.0 support.
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 confidenceThe vulnerability exists in the 802.1X (port-based network access control) component of macOS versions prior to 10.13.1. The issue stems from continued support for TLS 1.0, which has known cryptographic weaknesses including susceptibility to man-in-the-middle attacks and plaintext recovery. Attackers could potentially intercept or manipulate 802.1X authentication traffic to gain unauthorized network access.
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<= 10.13.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 macOS versionRun 'sw_vers -productVersion' in Terminal, or go to Apple menu > About This MacAffected if Version is 10.13.0 or earlier (any version below 10.13.1)
-
Confirm 802.1X is enabledOpen System Preferences > Network, select a network service (such as Ethernet), click the gear icon, choose 'Make Service Inactive' to check if 802.1X options appear. Alternatively, examine /Library/Preferences/SystemConfiguration/com.apple.network8021x.plist for configuration dataAffected if 802.1X authentication is configured or active on any network interface
-
Identify TLS configuration for 802.1XCapture network traffic during 802.1X authentication using a packet sniffer (such as tcpdump or Wireshark) and examine the TLS handshake messages. Look for the TLS protocol version in the ClientHello or ServerHello messagesAffected if TLS 1.0 is negotiated or allowed as a fallback during 802.1X authentication
A system is affected if it runs macOS 10.13.0 or earlier AND has 802.1X authentication enabled, because the 802.1X component will accept TLS 1.0 which has known cryptographic weaknesses.
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 · scopedUpgrade macOS to version 10.13.1 or later, which removes TLS 1.0 support from the 802.1X component. Alternatively, disable 802.1X authentication or implement additional network segmentation controls until systems can be patched.
macOS 10.13.1 or later
- Upgrade macOS to version 10.13.1 or later to address the TLS 1.0 vulnerability in the 802.1X component
- To upgrade: Open System Preferences > Software Update, or download the security update from Apple's support website
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13832 — 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-13832 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