dbcve.org
SafariWeb browser · Apple

CVE-2007-3186

HIGH · 9.3 CVSS v2.0 Published 2007-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Apple Safari Beta 3.0.1 for Windows allows remote attackers to execute arbitrary commands via shell metacharacters in a URI in the SRC of an IFRAME, as demonstrated using a gopher URI.

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

This vulnerability in Apple Safari Beta 3.0.1 for Windows allows remote command execution through shell metacharacters embedded in a URI specified within an IFRAME SRC attribute. The issue stems from insufficient input sanitization of URI schemes, specifically demonstrated with gopher:// URIs that can be interpreted by the shell.

MitigationOrganizations should immediately identify and update or remove installations of Safari Beta 3.0.1 for Windows, as no practical workaround exists for client-side browser vulnerabilities. Users should upgrade to stable, patched browser versions.

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
SafariWeb browser
Affected:all versions= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 3.0= 3.0.1

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Check if Apple Safari is installed on Windows
    Open Control Panel > Programs and Features (or Add/Remove Programs) and look for Apple Safari in the list of installed programs. Alternatively, check for the existence of C:\Program Files\Safari\ or C:\Program Files (x86)\Safari\
    Affected if Safari is found installed on the Windows system
  2. Determine the installed Safari version
    Launch Safari, then click Help > About Safari. The version number will be displayed in the About window (e.g., 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 3.0, or 3.0.1)
    Affected if The displayed version matches one of the affected versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 3.0, or 3.0.1
  3. Verify the operating system is Windows
    Right-click on My Computer or This PC and select Properties. Confirm the operating system is a Windows version (Windows XP, Vista, or later)
    Affected if The system is running Windows and Safari version is one of the affected versions listed above

The system is affected if Apple Safari version 2.0 through 3.0.1 is installed on a Windows operating system, as the vulnerability allows remote command execution via malicious URI schemes in IFRAME elements.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should immediately identify and update or remove installations of Safari Beta 3.0.1 for Windows, as no practical workaround exists for client-side browser vulnerabilities. Users should upgrade to stable, patched browser versions.

Recommended fix High confidence

Safari 3.0.2 or later (note: Safari for Windows was discontinued; migrate to Chrome/Firefox/Edge)

  1. 1. Discontinue use of Safari on Windows for internet browsing immediately due to this and other unpatched vulnerabilities
  2. 2. Migrate to an actively maintained browser (Chrome, Firefox, Edge) that receives regular security updates
  3. 3. If Safari is required for specific web development testing, use the latest macOS version with current Safari, which receives security patches
  4. 4. Apply any available Apple security updates if running older Safari versions on legacy systems
Caveat Safari for Windows is no longer maintained by Apple; users must switch to an alternative browser

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
4.0 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-2007-3186 — 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-2007-3186 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