CVE-2017-7088
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. The issue involves the "Exchange ActiveSync" component. It allows remote attackers to erase a device in opportunistic circumstances by hijacking a cleartext AutoDiscover V1 session during the setup of an Exchange account.
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 confidenceThe vulnerability exists in iOS Exchange ActiveSync account setup. During the AutoDiscover V1 process, the device sends credentials and configuration requests over cleartext HTTP, allowing a man-in-the-middle attacker on the same network to intercept the session and inject commands to remotely wipe the device.
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.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/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.
-
Identify iOS device versionCheck the iOS version on the device by navigating to Settings > General > About > Version. Confirm the exact version number displayed.Affected if The version is 10.3.3 or any earlier version (e.g., 10.3.2, 10.3.1, 10.0, 9.x, etc.)
-
Confirm Exchange ActiveSync account configurationOn the iOS device, go to Settings > Mail > Accounts > Add Account. Check if any Microsoft Exchange or Exchange ActiveSync account is configured.Affected if An Exchange ActiveSync account is present on the device and was set up using AutoDiscover
-
Verify AutoDiscover network transportInspect network traffic or review the Exchange server AutoDiscover DNS and IIS configuration to determine if the AutoDiscover V1 endpoint (https://autodiscover.domain.com/autodiscover/autodiscover.xml or HTTP fallback) is accessible over plain HTTP.Affected if AutoDiscover requests can traverse unencrypted HTTP (port 80) rather than being restricted to HTTPS (port 443)
-
Assess network trust levelDetermine whether the device has connected to untrusted or public networks (such as public WiFi hotspots) where a man-in-the-middle attacker could intercept HTTP traffic.Affected if The device has been or currently is connected to networks where interception is possible (unsecured WiFi, shared networks, etc.)
A user is affected if they are running iOS 10.3.3 or earlier, have an Exchange ActiveSync account configured via AutoDiscover, and have connected to networks where HTTP traffic could be intercepted.
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 dataUpdate affected iOS devices to version 11 or later. Additionally, enforce HTTPS for AutoDiscover and ensure devices connect only over trusted networks to prevent opportunistic interception attacks.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7088 — 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-7088 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