CVE-2011-0224
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 · uneditedCoreMedia in Apple Mac OS X through 10.6.8 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted QuickTime movie 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 · moderate confidenceA memory corruption vulnerability exists in CoreMedia framework in Apple Mac OS X through version 10.6.8. Attackers exploit this by tricking users into opening specially crafted QuickTime movie files, leading to arbitrary code execution or denial of service via memory corruption.
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.6.8= 10.0= 10.0.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.0= 10.1.1= 10.1.2= 10.1.3<= 10.6.8= 10.0= 10.0.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.0= 10.1.1= 10.1.2= 10.1.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
- 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 Mac OS X versionGo to Apple menu > About This Mac to view the exact version number, or run 'sw_vers' in TerminalAffected if The version shown is 10.6.8 or earlier, or matches any of these: 10.0, 10.0.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.1, 10.1.0, 10.1.1, 10.1.2, 10.1.3
-
Check your Mac OS X Server version if applicableRun 'sw_vers' in Terminal on server systems or check About This MacAffected if The server version is 10.6.8 or earlier, or matches any of the vulnerable 10.0.x or 10.1.x versions listed
-
Verify QuickTime is in useCheck if QuickTime player application exists in /Applications or run 'ps aux | grep -i quicktime' in TerminalAffected if QuickTime is installed and available on the system (the attack vector requires users to open malicious .mov files)
-
Confirm CoreMedia framework presenceRun 'ls /System/Library/Frameworks/CoreMedia.framework' in Terminal to verify the framework directory existsAffected if The CoreMedia.framework is present on the system (this is the vulnerable component)
You are affected if your Mac OS X or Mac OS X Server version is 10.6.8 or any earlier 10.0.x or 10.1.x version, and you use QuickTime to open movie 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 dataUpdate Mac OS X to a version beyond 10.6.8 that includes the patched CoreMedia framework, and exercise caution when opening QuickTime movie files from untrusted sources.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0224 — 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-2011-0224 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