CVE-2015-1098
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 · uneditediWork in Apple iOS before 8.3 and Apple OS X before 10.10.3 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted iWork file.
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 iWork (Numbers, Pages, Keynote) allows remote attackers to execute arbitrary code or cause denial of service via a specially crafted iWork file. The vulnerability exists in versions prior to iOS 8.3 and OS X 10.10.3.
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< 8.3< 10.10.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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 your operating systemDetermine whether the device runs iOS (iPhone/iPad) or OS X (Mac). This matters because the version thresholds differ between platforms.Affected if The device runs iOS or OS X.
-
Check iOS version on iPhone or iPadGo to Settings > General > About and look at the 'Version' field. If the version number is less than 8.3 (for example, 8.2, 8.1.x, or earlier), the system is in the vulnerable range.Affected if iOS version is below 8.3.
-
Check OS X version on MacClick the Apple menu > About This Mac. The version number displayed (such as 10.10.2, 10.10.1, or 10.10.0) must be 10.10.3 or later to not be affected.Affected if OS X version is below 10.10.3.
-
Verify iWork app versions on iOSOpen the App Store, go to the Updates tab, and check if any iWork apps (Pages, Numbers, Keynote) show available updates. Alternatively, long-press the app icon and tap Share > App Store link to view the version in the store page.Affected if iOS is below 8.3, regardless of iWork app version.
-
Verify iWork app versions on OS XOpen any iWork app (Pages, Numbers, Keynote), go to the app menu > About [App Name]. Compare the version number shown to the version that shipped with OS X 10.10.3 (which is Pages 5.5, Numbers 3.5, Keynote 6.5 or later).Affected if OS X is below 10.10.3, regardless of iWork app version.
You are affected if the device runs iOS below 8.3 or OS X below 10.10.3, regardless of which specific iWork app version is installed.
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 data8.310.10.3
Update iWork to version 8.3 or later on iOS, or 10.10.3 or later on OS X to remediate this vulnerability.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1098 — 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-1098 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