CVE-2014-4377
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 · uneditedInteger overflow in CoreGraphics in Apple iOS before 8 and Apple TV before 7 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted 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 · moderate confidenceInteger overflow vulnerability in CoreGraphics PDF parsing allows remote attackers to execute arbitrary code or cause denial of service via a specially crafted PDF document. The overflow occurs when processing malformed PDF content, potentially corrupting heap memory and enabling code execution.
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<= 6.2= 6.0= 6.0.1= 6.0.2= 6.1= 6.1.1= 6.1.2<= 7.1.2= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.1= 7.1.1<= 10.9.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.
-
Check iOS version on iPhone or iPadGo to Settings > General > About and look at the Version field. Compare this number against the affected iOS versions: 7.0 through 7.1.2, or any version <= 7.1.2Affected if The installed iOS version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.1, 7.1.1, 7.1.2, or any version <= 7.1.2
-
Check tvOS version on Apple TVGo to Settings > General > About and look at the Version field. Compare this number against the affected tvOS versions: 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1, 6.1.2, 6.2, or any version <= 6.2Affected if The installed tvOS version is 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1, 6.1.2, 6.2, or any version <= 6.2
-
Check macOS version on MacClick the Apple menu > About This Mac and look at the OS X version. Compare against affected versions: any OS X <= 10.9.4Affected if The installed OS X version is 10.9.4 or any version <= 10.9.4
-
Identify PDF processing usageReview whether the device or any application on it opens, previews, or processes PDF documents from external or untrusted sources. On iOS, this includes Mail attachments, Safari downloads, or third-party PDF viewers.Affected if The device processes PDF documents from untrusted sources and the OS version falls within the affected ranges above
A device is affected if it runs iOS 7.0-7.1.2 (or <=7.1.2), tvOS 6.0-6.2 (or <=6.2), or OS X 10.9.4 (or <=10.9.4) and processes PDF documents from 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 to iOS 8 or later and Apple TV 7 or later to remediate. Users should avoid opening PDF documents from untrusted sources until devices are patched.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4377 — 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-4377 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