dbcve.org
Mac Os XOperating system · Apple

CVE-2006-3504

MEDIUM · 5.1 CVSS v2.0 Published 2006-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
The Download Validation in LaunchServices for Apple Mac OS X 10.4.7 can identify certain HTML as "safe", which could allow attackers to execute Javascript code in local context when the "Open 'safe' files after downloading" option is enabled in Safari.

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

The Download Validation component in LaunchServices for Mac OS X 10.4.7 incorrectly identifies certain HTML files as 'safe'. When the 'Open safe files after downloading' setting is enabled in Safari, these HTML files automatically open and execute JavaScript in the local file context rather than the browser sandbox, allowing potential local code execution.

MitigationDisable the 'Open safe files after downloading' option in Safari preferences, or upgrade to a patched version of Mac OS X beyond 10.4.7.

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.4.7
Mac Os X ServerOperating system
Affected:= 10.4.7

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
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/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. Confirm Mac OS X version is 10.4.7
    Run 'sw_vers -productVersion' in Terminal or check About This Mac
    Affected if The version shown is exactly 10.4.7 (not 10.4.8 or higher, not lower than 10.4.7)
  2. Check if Safari 'Open safe files after downloading' is enabled
    Run 'defaults read com.apple.Safari AutoOpenSafeDownloads' in Terminal
    Affected if The command returns 1 (enabled); if it returns 0 or the key does not exist, the setting is disabled and the attack surface does not exist

You are affected only if running Mac OS X 10.4.7 AND the Safari preference 'Open safe files after downloading' is set to enabled (value of 1).

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

Disable the 'Open safe files after downloading' option in Safari preferences, or upgrade to a patched version of Mac OS X beyond 10.4.7.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.5 hours of engineering $750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-3504 — 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-2006-3504 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