CVE-2015-7107
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 · uneditedQuickLook in Apple iOS before 9.2 and OS X before 10.11.2 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted iWork file.
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 exists in Apple's QuickLook framework that processes iWork files (Pages, Numbers, Keynote documents). When QuickLook parses a specially crafted malicious iWork file, it can be triggered into executing arbitrary code or causing a denial of service through memory corruption. The vulnerability affects iOS devices before version 9.2 and Mac systems running OS X before version 10.11.2.
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.11.1<= 9.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 the installed Mac OS X versionRun 'sw_vers -productVersion' in Terminal or check System Preferences > About > VersionAffected if The version is 10.11.1 or lower (any version up to and including 10.11.1)
-
Check the installed iOS version on iPhone/iPadOn the device, go to Settings > General > About > Version. For bulk enterprise checking, use MDM software or Apple Configurator to query the iOS versionAffected if The version is 9.1 or lower (any version up to and including 9.1)
-
Verify QuickLook functionality is available on the systemOn Mac, try pressing Space on any file in Finder to invoke Quick Look, or run 'qlmanage -p' on a test file. On iOS, QuickLook runs automatically when previewing attachments in Mail or other appsAffected if QuickLook is functional and can process iWork files (Pages, Numbers, Keynote documents)
-
Confirm the system processes iWork documentsCheck if the user has any Pages, Numbers, or Keynote documents on the system, or check Spotlight/Quick Look thumbnail generation logsAffected if iWork documents exist and QuickLook would parse them
A system is affected if it runs OS X 10.11.1 or earlier, or iOS 9.1 or earlier, AND has QuickLook enabled to process iWork documents.
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 dataApply the vendor-supplied security updates: upgrade iOS devices to version 9.2 or later, and Mac systems to OS X 10.11.2 (El Capitan) or later. For enterprise environments, deploy these updates via mobile device management (MDM) or software update mechanisms.
- Consultation3.0 h
- Implementation6.0 h
- Testing2.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 $3,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7107 — 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-7107 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