CVE-2014-4350
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 QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted MIDI file.
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 in QT Media Foundation in Apple OS X versions prior to 10.9.5 allows remote attackers to execute arbitrary code or cause denial of service via a crafted MIDI file containing malformed data that overflows a buffer during parsing.
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= 10.7.5= 10.8.5= 10.9= 10.9.1= 10.9.2= 10.9.3= 10.9.4= 10.7.5CVSS 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 your OS X versionClick Apple menu > About This Mac. The version number is displayed below the macOS name (e.g., 10.9.4, 10.9.5, etc.).Affected if The installed version is 10.7.5, 10.8.5, 10.9, 10.9.1, 10.9.2, 10.9.3, or 10.9.4 (OS X Server 10.7.5 is also affected). Versions 10.9.5 and later are not affected.
-
Confirm QT Media Foundation is presentThis component is part of the core QuickTime framework in OS X. It is present by default in affected OS X versions. No manual check needed if OS X version is confirmed.Affected if QT Media Foundation is included by default in all affected OS X versions listed above.
-
Identify if MIDI file processing occursReview what applications on the system can open or process MIDI files (e.g., GarageBand, Logic Pro, QuickTime Player, third-party audio software). Check recent file access logs if available.Affected if The vulnerability is triggered when parsing a crafted MIDI file. If no applications process MIDI files, the attack surface is reduced, but the system is still vulnerable if running an affected OS X version.
You are affected if your installed OS X version is 10.7.5, 10.8.5, 10.9, 10.9.1, 10.9.2, 10.9.3, or 10.9.4 (or OS X Server 10.7.5) and you have applications that can parse MIDI 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 dataUpgrade to OS X 10.9.5 or later which contains the security fix for this vulnerability.
- Consultation2.0 h
- Implementation4.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4350 — 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-4350 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