CVE-2017-7108
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. iOS before 11 is affected. tvOS before 11 is affected. watchOS before 4 is affected. The issue involves the "Wi-Fi" component. It might allow remote attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via crafted Wi-Fi traffic.
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 memory corruption vulnerability in the Wi-Fi component of iOS, tvOS, and watchOS allows remote attackers to execute arbitrary code via crafted Wi-Fi traffic. The flaw exists in the Wi-Fi stack's handling of maliciously crafted network packets, potentially giving attackers privileged code execution or 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<= 10.3.3<= 10.2.2<= 3.2.3CVSS 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.
-
Identify the device typeDetermine whether the device is an iPhone/iPad (iOS), Apple TV (tvOS), or Apple Watch (watchOS). This determines which version range applies.Affected if Device is an iPhone, iPad, Apple TV, or Apple Watch running the affected operating systems.
-
Check iOS version on iPhone or iPadOn the device, go to Settings > General > About and note the Version number. Compare this to the affected range of 10.3.3 and below.Affected if The iOS version is 10.3.3 or lower.
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About > Version. Compare this to the affected range of 10.2.2 and below.Affected if The tvOS version is 10.2.2 or lower.
-
Check watchOS version on Apple WatchOn Apple Watch, open the Watch app on paired iPhone, go to General > About, and note the watchOS version. Compare to affected range of 3.2.3 and below.Affected if The watchOS version is 3.2.3 or lower.
-
Confirm Wi-Fi is enabledCheck if Wi-Fi is turned on in the device settings. The vulnerability is triggered via crafted Wi-Fi network traffic.Affected if Wi-Fi is enabled on a device running an affected OS version.
A device is affected if it runs iOS 10.3.3 or lower, tvOS 10.2.2 or lower, or watchOS 3.2.3 or lower, and has Wi-Fi functionality enabled.
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 · scopedUpdate all affected iOS, tvOS, and watchOS devices to version 11 or later. For devices that cannot be updated, consider network segmentation to limit Wi-Fi attack surface and monitor for unusual Wi-Fi activity.
iOS 11+, tvOS 11+, watchOS 4+
- Back up your iPhone, iPad, or iPod touch before upgrading
- Connect your device to power and Wi-Fi
- Go to Settings > General > Software Update
- If iOS 11 or later is available, tap Download and Install
- For Apple Watch, pair with iPhone and open Watch app > General > Software Update > Download and Install watchOS 4 or later
- For Apple TV, go to Settings > System > Software Updates > Update Software > Download and Install tvOS 11 or later
- Ensure the device remains connected to power until the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7108 — 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-7108 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