CVE-2014-1275
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 · uneditedBuffer overflow in ImageIO in Apple iOS before 7.1 and Apple TV before 6.1 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via crafted JPEG2000 data in a PDF 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 confidenceBuffer overflow vulnerability in Apple's ImageIO framework when parsing crafted JPEG2000 image data embedded in PDF documents. The flaw allows remote attackers to achieve arbitrary code execution or cause application crashes by tricking users into opening malicious PDF 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<= 7.0.6= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5<= 6.0.2= 6.0= 6.0.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
- 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 the device type and operating systemDetermine whether the device is an iPhone, iPad, or iPod touch running iOS, or an Apple TV running tvOS. Note the exact OS name and version installed.Affected if Device is an iPhone, iPad, or iPod touch running iOS, or an Apple TV running tvOS
-
Check iOS version on iPhone, iPad, or iPod touchGo to Settings > General > About on the device and note the Version number. Compare this to the affected iOS versions: 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, or 7.0.6.Affected if iOS version is 7.0.x or any version 7.0.6 or lower
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About > Version. Compare this to the affected tvOS versions: 6.0, 6.0.1, 6.0.2, or any version 6.0.2 or lower.Affected if tvOS version is 6.0.x or any version 6.0.2 or lower
-
Verify ImageIO framework presenceThe vulnerability exists in the ImageIO framework. On iOS/tvOS devices, this framework handles image parsing including JPEG2000 data embedded in PDF documents. There is no user-accessible setting to disable this framework.Affected if Device runs a vulnerable iOS or tvOS version listed above - the ImageIO framework automatically processes JPEG2000 images in PDFs when opened
If the device is an iPhone, iPad, or iPod touch running iOS 7.0 through 7.0.6, or an Apple TV running tvOS 6.0 through 6.0.2, the ImageIO framework is vulnerable when parsing crafted JPEG2000 image data in PDF files.
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 affected devices to iOS 7.1 or later and Apple TV 6.1 or later to obtain the patched ImageIO component. For enterprise environments, deploy OS updates via MDM and verify complete coverage.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1275 — 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-2014-1275 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