CVE-2006-2277
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 · uneditedMultiple Apple Mac OS X 10.4 applications might allow context-dependent attackers to cause a denial of service (application crash) via a crafted OpenEXR (.exr) image file, which triggers the crash when opening a folder using Finder, displaying the image in Safari, or using Preview to open the 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 confidenceMultiple Mac OS X 10.4 applications (Finder, Safari, Preview) crash when processing a maliciously crafted OpenEXR (.exr) image file, causing denial of service. The vulnerability is triggered when the system processes the malformed .exr file through any of these applications.
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.4= 10.4.1= 10.4.2= 10.4.3= 10.4.4= 10.4.5= 10.4.6CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 the installed Mac OS X versionOpen System Profiler (or System Information) and look at the Mac OS X version, or run 'sw_vers' in TerminalAffected if The version shows 10.4.0 through 10.4.6 (any of 10.4, 10.4.1, 10.4.2, 10.4.3, 10.4.4, 10.4.5, or 10.4.6)
-
Verify if OpenEXR file support is presentSearch for the OpenEXR framework library at /System/Library/Frameworks/OpenEXR.framework, or attempt to identify if .exr files are recognized by the system (file command on a sample .exr file)Affected if The OpenEXR framework exists and .exr files are recognized as valid image files by the system
-
Confirm whether Apple security update 2006-004 has been appliedOpen System Preferences > Software Update, or check the installed updates via 'ls /Library/Receipts' for the receipt named similar to 'SecurityUpdate-2006-004' or 'SecurityUpdate2006-004.pkg'Affected if The specific security update for this CVE is not listed in installed updates, meaning the system remains unpatched
A user is affected if their Mac OS X version is 10.4.x and the security update has not been installed, meaning the system can crash when processing malicious .exr files through Finder, Safari, or Preview.
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 dataApply Apple's security update for Mac OS X 10.4 that addresses this vulnerability; avoid opening .exr files from untrusted sources until patched.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2277 — 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-2006-2277 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