CVE-2015-7034
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 Apple iWork application before 2.6 for iOS and Apple Pages before 5.6 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Pages document.
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 confidenceMemory corruption vulnerability in Apple Pages (iWork) for iOS allows remote code execution or DoS via maliciously crafted .pages documents. The vulnerability exists in versions before iWork 2.6 and Pages 5.6, exploiting how the application parses specially crafted document files.
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<= 2.5.4<= 5.5.3CVSS 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 Apple Pages version on iOSOpen the App Store app, tap your profile icon, scroll to Purchased, find Pages, and note the version number. Alternatively, go to Settings > General > iPhone Storage > find Pages in the list and view its version info.Affected if The listed version is 5.5.3 or lower (vulnerable). Version 5.6 or later is patched.
-
Check Apple iWork version on iOSOpen the App Store app, tap your profile icon, scroll to Purchased, find iWork (or the specific iWork app: Numbers, Keynote), and note the version number. Alternatively, go to Settings > General > iPhone Storage > find the iWork app and view its version info.Affected if The listed version is 2.5.4 or lower (vulnerable). Version 2.6 or later is patched.
-
Verify iOS version compatibilityGo to Settings > General > About to view the iOS version. Note that older iOS devices may not support the patched versions of Pages and iWork.Affected if The iOS version is too old to run Pages 5.6 or iWork 2.6, leaving the vulnerable app versions in place.
-
Confirm document handling exposureDetermine if the device receives .pages documents via email, web downloads, AirDrop, or third-party apps. The vulnerability triggers when opening specially crafted .pages files.Affected if The device opens .pages files from untrusted sources and runs a vulnerable version of Pages or iWork.
You are affected if either Apple Pages version is 5.5.3 or lower, or iWork version is 2.5.4 or lower, AND the device processes .pages documents from potentially untrusted sources.
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 dataUpdate Apple Pages and iWork applications to version 5.6 or later for Pages and 2.6 or later for iWork to obtain the patched versions. Ensure iOS devices are running supported versions capable of receiving these updates.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7034 — 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-7034 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