dbcve.org
Mac Os XOperating system · Apple

CVE-2015-6995

MEDIUM · 6.8 CVSS v2.0 Published 2015-10-23
Fix available
A fix is available. Upgrade to after 10.11.0 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Disk Images component in Apple iOS before 9.1 and OS X before 10.11.1 misparses images, which allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted app.

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 confidence

The Disk Images component in Apple iOS and OS X contains a parsing vulnerability when handling disk images, leading to memory corruption. Attackers can exploit this by tricking users into opening or mounting a specially crafted disk image file through a malicious app, potentially achieving arbitrary code execution.

MitigationApply the vendor-supplied patches by updating iOS to version 9.1 or later and OS X to version 10.11.1 or later.

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
Mac Os XOperating system
Affected:<= 10.11.0
Iphone OsOperating system
Affected:<= 9.0.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the operating system
    On Mac: click Apple menu > About This Mac to see the version number. On iOS: go to Settings > General > About to see the iOS version.
    Affected if The system is running Apple OS X or iOS
  2. Compare your OS X version against the affected range
    If running OS X, note the version number (for example, 10.11.0, 10.10.5, etc.) and compare to 10.11.0 - any version equal to or below 10.11.0 is affected.
    Affected if OS X version is 10.11.0 or lower
  3. Compare your iOS version against the affected range
    If running iOS, note the version number (for example, 9.0.2, 9.0.1, etc.) and compare to 9.0.2 - any version equal to or below 9.0.2 is affected.
    Affected if iOS version is 9.0.2 or lower
  4. Confirm Disk Images component presence
    The Disk Images component is a built-in system component for handling .dmg and .iso files. On OS X, you can verify the system can mount disk images by attempting to open a .dmg file in Finder.
    Affected if The system can mount or open disk image files (this is the default behavior on unpatched systems)

You are affected if your device runs OS X 10.11.0 or lower, or iOS 9.0.2 or lower, and the Disk Images component (used for mounting .dmg files) is functional on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 10.11.0
Interim mitigation

Apply the vendor-supplied patches by updating iOS to version 9.1 or later and OS X to version 10.11.1 or later.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6995 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6995 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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