dbcve.org
Mac Os XOperating system · Apple

CVE-2014-1391

MEDIUM · 6.8 CVSS v2.0 Published 2014-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted movie file with RLE encoding.

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 confidence

Memory corruption vulnerability in QT Media Foundation in Apple OS X versions before 10.9.5 allows remote attackers to execute arbitrary code or cause denial of service via a crafted movie file using Run-Length Encoding (RLE).

MitigationUpdate affected systems to OS X 10.9.5 or later to patch the vulnerability. Avoid opening untrusted or unfamiliar movie files until the patch is applied.

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
Mac Os XOperating system
Affected:= 10.7.5= 10.8.5= 10.9= 10.9.1= 10.9.2= 10.9.3= 10.9.4
Mac Os X ServerOperating system
Affected:= 10.7.5

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

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

  1. Identify installed OS X version
    Click Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if The version displayed is 10.7.5, 10.8.5, 10.9, 10.9.1, 10.9.2, 10.9.3, or 10.9.4
  2. Confirm OS X Server variant if applicable
    Check system profile or run 'sw_vers -productVersion' and verify if Server variant is running
    Affected if Running Apple Mac OS X Server version 10.7.5 specifically
  3. Identify QuickTime component presence
    Check for QuickTime installation via 'ls /Applications | grep -i quicktime' or system profiler
    Affected if QuickTime is installed and the system is running an affected OS X version listed above

The system is vulnerable if it is running any of the listed OS X versions (10.7.5 through 10.9.4) with QuickTime component present, and an attacker could exploit it by tricking a user into opening a crafted RLE-encoded movie file.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected systems to OS X 10.9.5 or later to patch the vulnerability. Avoid opening untrusted or unfamiliar movie files until the patch is applied.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1391 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