CVE-2017-13806
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 "Profiles" component. It does not enforce the configuration profile's settings for whether pairings are allowed.
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 Profiles component in iOS versions prior to 11 fails to enforce configuration profile settings that control whether device pairings are allowed, potentially allowing unauthorized pairings despite administrator-defined policies.
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< 11.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 iOS versionNavigate to Settings > General > About > Version on the iOS device, or use Apple Configurator, Xcode, or an MDM solution to query the device's iOS versionAffected if The device is running iOS version 10.x or lower (versions prior to 11.0)
-
Identify installed configuration profilesNavigate to Settings > General > Device Management (or Profile Management on older iOS versions) to view installed configuration profiles, or query through Apple Configurator or an MDM solutionAffected if One or more configuration profiles are installed on the device
-
Inspect pairing-related profile payloadExamine the installed configuration profiles for any Mobile Device Management (MDM) payloads or Profile Service payloads that contain pairing restrictions or device pairing rules. Use Apple Configurator or MDM tools to view the full profile payload contentsAffected if A configuration profile contains settings to restrict or control device pairing (such as PairingMode set to Disabled or similar pairing control payloads)
-
Verify pairing behavior against policyAttempt to initiate pairing between the iOS device and a computer using Finder/iTunes, or review MDM enrollment and pairing logs to determine if pairing occurred when a pairing-restriction profile was present on iOS versions below 11Affected if Pairing succeeds or MDM logs show unauthorized pairing events occurred despite a configuration profile attempting to block pairing on an affected iOS version
A device is affected if it runs iOS versions prior to 11.0 AND has a configuration profile installed that attempts to restrict device pairing, as the vulnerability allows pairing to succeed despite the administrator-defined policy.
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 data11.0
Update affected iOS devices to version 11 or later to ensure configuration profile settings regarding pairing permissions are properly enforced.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13806 — 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-13806 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