dbcve.org
Iphone OsOperating system · Apple

CVE-2015-7037

MEDIUM · 5.0 CVSS v2.0 Published 2015-12-11
Fix available
A fix is available. Upgrade to after 9.1 or later.
See remediation →
59/100
Remediation priority · Elevated
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
Directory traversal vulnerability in Mobile Backup in Photos in Apple iOS before 9.2 allows attackers to read arbitrary files via a crafted pathname.

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

Directory traversal vulnerability in Mobile Backup within the Photos application in Apple iOS versions prior to 9.2 allows attackers to read arbitrary files on the device filesystem by using specially crafted pathnames containing traversal sequences (such as '../'). This is a path traversal issue in the backup functionality that enables unauthorized file access.

MitigationUpdate iOS devices to version 9.2 or later to remediate this vulnerability. For enterprise environments, use mobile device management (MDM) tools to identify and update any devices running iOS versions prior to 9.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
Iphone OsOperating system
Affected:<= 9.1

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
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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. Check the iOS version installed on the device
    Go to Settings > General > About on the iOS device and locate the Version field, or use an MDM tool or iTunes to query the device OS version
    Affected if The version displays a number lower than 9.2 (for example 9.1, 9.0.x, 8.x, or earlier)
  2. Confirm the Photos application is present
    Locate the Photos app icon on the iOS home screen - this app is pre-installed on all iOS devices
    Affected if The Photos application exists on the device (this is true for all standard iOS installations)
  3. Verify Mobile Backup functionality is accessible
    Navigate to Settings > Photos & Camera or check iCloud backup settings to confirm Mobile Backup or iCloud Photo Library features are enabled
    Affected if Mobile Backup or iCloud photo backup features are turned on, making the vulnerable backup component active on the device

The device is affected if it runs any iOS version earlier than 9.2 and has the Photos application with Mobile Backup functionality available or enabled.

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 9.1
Interim mitigation

Update iOS devices to version 9.2 or later to remediate this vulnerability. For enterprise environments, use mobile device management (MDM) tools to identify and update any devices running iOS versions prior to 9.2.

Fix this in Iphone Os 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-7037 — 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-7037 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