CVE-2015-7068
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 · uneditedIOKit SCSI in Apple iOS before 9.2, OS X before 10.11.2, tvOS before 9.1, and watchOS before 2.1 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (NULL pointer dereference) via an app that provides an unspecified userclient type.
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 confidenceIOKit SCSI kernel driver vulnerability allowing arbitrary code execution in privileged context or NULL pointer dereference DoS via malicious app providing unspecified userclient type.
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< 9.2< 2.1< 9.1< 10.11.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 Apple operating system productDetermine if the system is running iOS, macOS (OS X), tvOS, or watchOS. This can be done via system reports or device type identification.Affected if The system is any Apple device running one of these operating systems.
-
Check the installed iOS versionOn iPhone or iPad, go to Settings > General > About and note the Version number. Compare it to the affected range: versions below 9.2 are vulnerable.Affected if iOS version is lower than 9.2.
-
Check the installed macOS (OS X) versionOn Mac, click the Apple menu > About This Mac. Note the OS X version number. Compare it to the affected range: versions below 10.11.2 are vulnerable.Affected if macOS (OS X) version is lower than 10.11.2.
-
Check the installed tvOS versionOn Apple TV, go to Settings > General > About. Note the version number. Compare to the affected range: versions below 9.1 are vulnerable.Affected if tvOS version is lower than 9.1.
-
Check the installed watchOS versionOn Apple Watch, open the Watch app on paired iPhone > General > About. Note the watchOS version. Compare to the affected range: versions below 2.1 are vulnerable.Affected if watchOS version is lower than 2.1.
A system is affected if it is running any of the listed Apple OS products at a version lower than the patched thresholds (iOS 9.2, OS X 10.11.2, tvOS 9.1, watchOS 2.1), as the vulnerability exists in the IOKit SCSI kernel driver regardless of specific configuration.
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 data2.19.19.2
Apply vendor patches: iOS 9.2+, OS X 10.11.2+, tvOS 9.1+, watchOS 2.1+. Prioritize patching given kernel-level privilege escalation and DoS vectors.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7068 — 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-2015-7068 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