TvosOperating system · Apple

CVE-2014-1359

HIGH · 10.0 CVSS v2.0 Published 2014-07-01
Fix available
A fix is available. Upgrade to after 7.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
Integer underflow 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.

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 confidence

Integer underflow vulnerability in launchd (Apple's system initialization and service management daemon) in iOS before 7.1.2, OS X before 10.9.4, and Apple TV before 6.1.2 allows attackers to execute arbitrary code via a crafted malicious application.

MitigationApply Apple's security updates: upgrade iOS to 7.1.2 or later, OS X to 10.9.4 or later, or Apple TV to 6.1.2 or later.

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
TvosOperating system
Affected:<= 6.1.1= 6.0= 6.0.1= 6.0.2= 6.1
Iphone OsOperating system
Affected:<= 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
Mac Os XOperating system
Affected:= 10.9= 10.9.1= 10.9.2= 10.9.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version on iPhone or iPad
    Go to Settings > General > About and look at the Version field, or run 'sw_vers' command in terminal if jailbroken
    Affected if 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 7.1.1 (any version before 7.1.2)
  2. Check OS X version on Mac
    Click Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if Version is 10.9, 10.9.1, 10.9.2, or 10.9.3 (any version before 10.9.4)
  3. Check Apple TV version
    Go to Settings > General > About > Version on Apple TV, or check via iTunes if jailbroken
    Affected if Version is 6.0, 6.0.1, 6.0.2, 6.1, or 6.1.1 (any version before 6.1.2)
  4. Verify launchd is running (optional confirmation)
    Run 'launchctl list' command in terminal or check processes in Activity Monitor for /sbin/launchd
    Affected if launchd is present and running, which is the default state on affected Apple systems

You are affected if your iOS, OS X, or Apple TV version matches any of the vulnerable versions listed (7.1.1 or earlier for iOS, 10.9.3 or earlier for OS X, 6.1.1 or earlier for Apple TV).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 7.1.1
Interim mitigation

Apply Apple's security updates: upgrade iOS to 7.1.2 or later, OS X to 10.9.4 or later, or Apple TV to 6.1.2 or later.

Recommended fix High confidence

iOS 7.1.2 (or later), OS X 10.9.4 (or later), or tvOS 6.1.2 (or later) depending on device

  1. Identify the affected device type (iPhone/iPad, Mac, or Apple TV)
  2. Determine the current installed version from Settings > General > About (iOS) or System Preferences > Software Update (Mac) or Settings > General > About (Apple TV)
  3. Back up all important data on the device before upgrading
  4. For iOS devices: Upgrade to iOS 7.1.2 or later via Settings > General > Software Update
  5. For Mac computers: Upgrade to OS X 10.9.4 or later via Mac App Store or Apple Software Update
  6. For Apple TV: Upgrade to tvOS 6.1.2 or later via Settings > General > Update Software
  7. Verify the upgrade was successful by confirming the new version number in the device settings
Caveat Standard upgrade considerations - ensure backups exist before updating; verify app compatibility with newer iOS/OS X versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tvos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1359 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1359 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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