CVE-2017-7086
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. macOS before 10.13 is affected. tvOS before 11 is affected. watchOS before 4 is affected. The issue involves the "libc" component. It allows remote attackers to cause a denial of service (resource consumption) via a crafted string that is mishandled by the glob function.
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 confidenceA denial of service vulnerability exists in the libc library's glob function across multiple Apple operating systems (iOS, macOS, tvOS, watchOS). Remote attackers can exploit this by sending a crafted string that causes excessive resource consumption when processed by the glob pattern-matching function, potentially leading to system unavailability.
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.12.6<= 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 the installed iOS versionGo to Settings > General > About and note the version number under VersionAffected if The version is 10.3.3 or earlier
-
Identify the installed macOS versionClick the Apple menu > About This Mac and note the version under macOSAffected if The version is 10.12.6 or earlier (10.12.x versions before 10.12.6)
-
Identify the installed tvOS versionGo to Settings > General > About > Version on Apple TVAffected if The version is 10.2.2 or earlier
-
Identify the installed watchOS versionOpen the Watch app on iPhone, go to My Watch > General > AboutAffected if The version is 3.2.3 or earlier
-
Verify applications using libc glob functionReview any custom or third-party applications that process user-supplied file path patterns using the glob functionAffected if An application uses glob with untrusted input and the OS version falls within the affected ranges above
The system is affected if it runs iOS 10.3.3 or earlier, macOS 10.12.6 or earlier, tvOS 10.2.2 or earlier, or watchOS 3.2.3 or earlier, and an application invokes the libc glob function with attacker-controlled patterns.
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 dataUpgrade affected systems to iOS 11 or later, macOS 10.13 or later, tvOS 11 or later, or watchOS 4 or later to patch the vulnerable libc glob implementation.
- Consultation6.0 h
- Implementation12.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7086 — 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-7086 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