CVE-2015-5847
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 · uneditedThe Disk Images component in Apple iOS before 9 allows local users to gain privileges or cause a denial of service (memory corruption) via unspecified vectors.
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 local privilege escalation and memory corruption vulnerability in the Disk Images component of Apple iOS versions prior to 9. The vulnerability allows a local attacker to potentially gain elevated privileges or cause a denial of service through memory corruption via unspecified vectors.
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.10.5= 1.0<= 8.4.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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 iOS versionGo to Settings > General > About on the iOS device and note the Version number. Alternatively, connect the device to a computer with iTunes or Finder and check the device summary page for the iOS version.Affected if The version is 8.4.1 or lower, or any version prior to 9.0 (e.g., 8.4, 8.3, 8.2, etc.)
-
Check the installed Mac OS X versionClick the Apple menu in the top-left corner, select About This Mac, and note the version number displayed under the macOS name.Affected if The version is 10.10.5 or lower (e.g., 10.10.4, 10.10.3, etc.)
-
Check the installed watchOS versionOpen the Watch app on the paired iPhone, go to General > About, and note the watchOS version.Affected if The version is exactly 1.0 (the only affected watchOS version)
-
Verify Disk Images functionality is accessibleOn iOS, check if the device supports mounting or interacting with disk images. On macOS, verify if Disk Utility or diskimgutil tools are available and the system can process disk images.Affected if The Disk Images component (diskimgutil, Disk Utility, or related services) is present and operational on the device
The environment is affected if the installed OS version falls within the affected ranges (iOS <= 8.4.1, Mac OS X <= 10.10.5, watchOS 1.0) and the Disk Images component is accessible on the device.
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 iOS devices to version 9 or later to address this vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5847 — 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-5847 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