CVE-2015-7033
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, Apple Keynote before 6.6, Apple Pages before 5.6, and Apple Numbers before 3.6 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted 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's iWork suite (Keynote, Pages, Numbers) for iOS. Processing a specially crafted malicious document triggers memory corruption that can lead to arbitrary code execution or application crash (denial of service).
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<= 3.5<= 5.5.3<= 6.5<= 2.5.4CVSS 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.
-
Identify installed iWork apps on iOS deviceCheck the iOS device for installed applications: Keynote, Pages, Numbers, or the bundled iWork package. Use mobile device management (MDM) software, Apple Configurator, or manually inspect the device's installed apps list.Affected if Any of these apps are present on the device
-
Check Keynote versionOpen the App Store, go to Updates > Purchased, or use MDM/Apple Configurator to view the installed version of Keynote. The version number is displayed in the app information.Affected if Version is 6.5 or earlier
-
Check Pages versionOpen the App Store, go to Updates > Purchased, or use MDM/Apple Configurator to view the installed version of Pages. The version number is displayed in the app information.Affected if Version is 5.5.3 or earlier
-
Check Numbers versionOpen the App Store, go to Updates > Purchased, or use MDM/Apple Configurator to view the installed version of Numbers. The version number is displayed in the app information.Affected if Version is 3.5 or earlier
-
Check bundled iWork package versionIf iWork was installed as a bundled package (iWork 2.5.4 or earlier), check the package version through the App Store or device management tools.Affected if Version is 2.5.4 or earlier
A user is affected if any installed iWork app (Keynote <=6.5, Pages <=5.5.3, Numbers <=3.5, or iWork bundle <=2.5.4) is present on the iOS 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 dataUpdate iWork for iOS to version 2.6+, Keynote to 6.6+, Pages to 5.6+, and Numbers to 3.6+ or later. Avoid opening documents from untrusted or unknown sources.
- 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-7033 — 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-7033 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