CVE-2014-1357
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 · uneditedHeap-based buffer overflow in launchd in Apple iOS before 7.1.2, Apple OS X before 10.9.4, and Apple TV before 6.1.2 allows attackers to execute arbitrary code via a crafted application that generates log messages.
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 confidenceHeap-based buffer overflow in launchd, Apple's service manager/init system. A crafted application that generates specially crafted log messages can overflow a heap buffer, allowing arbitrary code execution with elevated privileges. Affects iOS <7.1.2, OS X <10.9.4, and Apple TV <6.1.2.
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.1.1= 6.0= 6.0.1= 6.0.2= 6.1<= 7.1.1= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.1= 10.9= 10.9.1= 10.9.2= 10.9.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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Apple platformDetermine if the system is iOS, macOS (OS X), or Apple TV. On iOS, go to Settings > General > About. On macOS, click the Apple menu > About This Mac. On Apple TV, go to Settings > General > About.Affected if The device is running Apple iPhone OS, Apple Mac OS X, or Apple TVos.
-
Check iOS versionOn iOS devices, go to Settings > General > About and note the Version number.Affected if The version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.1, or any version 7.1.1 or lower.
-
Check macOS (OS X) versionOn Mac systems, click the Apple menu and select About This Mac. Note the version number (for example, 10.9, 10.9.1, 10.9.2, or 10.9.3).Affected if The version is exactly 10.9, 10.9.1, 10.9.2, or 10.9.3.
-
Check Apple TV versionOn Apple TV, go to Settings > General > About and note the software version.Affected if The version is 6.0, 6.0.1, 6.0.2, 6.1, or any version 6.1.1 or lower.
The system is affected if it is running iOS 7.1.1 or earlier, OS X 10.9.3 or earlier, or Apple TV 6.1.1 or earlier.
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.
dbcve · scopedApply vendor-supplied patches by updating to iOS 7.1.2 or later, OS X 10.9.4 or later, or Apple TV 6.1.2 or later. For legacy systems that cannot be updated, consider network segmentation to limit exposure.
iOS 7.1.2 or later; OS X 10.9.4 or later; tvOS 6.1.2 or later
- For iOS devices: Navigate to Settings > General > Software Update and upgrade to iOS 7.1.2 or later
- For Mac OS X systems: Go to Apple menu > Software Update and install OS X 10.9.4 or later
- For Apple TV: Go to Settings > General > Software Update and update to version 6.1.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1357 — 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-1357 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