CVE-2015-7070
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 · uneditedMobile Replayer in GPUTools Framework in Apple iOS before 9.2 allows attackers to execute arbitrary code in a privileged context via an app that provides a crafted pathname, a different vulnerability than CVE-2015-7069.
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 confidenceThe Mobile Replayer component in the GPUTools Framework in Apple iOS before version 9.2 contains a vulnerability that allows arbitrary code execution in a privileged context. Attackers can exploit this by crafting a malicious pathname through a malicious app, enabling them to escape application sandboxing and execute code with elevated privileges.
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.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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 iOS version on the deviceGo to Settings > General > About > Version on the iOS device, or connect to Xcode and check the device infoAffected if Version displays 9.1 or lower (for example, 9.0, 8.x, etc.)
-
Verify the GPUTools Framework is presentThis framework is included by default in iOS and cannot be disabled; it is present on all iOS devices running versions <= 9.1Affected if The framework exists as a system component in the affected iOS version range
-
Determine if untrusted third-party apps could be installedCheck if the device allows installation of apps from untrusted sources (Settings > General > Profiles & Device Management on enterprise devices, or if sideloading is enabled)Affected if The device has enterprise profiles from unknown developers or has sideloading enabled, allowing potential malicious apps to be installed
-
Assess device jailbreak statusCheck if the device has been jailbroken, which bypasses sandboxing protectionsAffected if The device is jailbroken, indicating sandboxing may already be compromised
The device is affected if it runs iOS version 9.1 or lower and a malicious app could be installed, since the Mobile Replayer vulnerability in GPUTools allows sandbox escape and privileged code execution.
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.
dbcve · scopedUpdate all affected iOS devices to version 9.2 or later to remediate this vulnerability. For enterprise environments, deploy the update through mobile device management (MDM) solutions.
iOS 9.2 or later
- Backup your device data using iTunes or iCloud
- Connect your iOS device to a computer with iTunes
- Check for and install iOS 9.2 or later via Settings > General > Software Update (or through iTunes)
- After updating, verify the iOS version is 9.2 or later in Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7070 — 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-7070 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