dbcve.org
SafariWeb browser · Apple

CVE-2007-3514

HIGH · 8.5 CVSS v2.0 Published 2007-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
Cross-domain vulnerability in Apple Safari for Windows 3.0.2 allows remote attackers to bypass the Same Origin Policy and access restricted information from other domains via JavaScript that overwrites the document variable and statically sets the document.domain attribute to a file:// location, a different vector than CVE-2007-3482.

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 is a Same Origin Policy bypass vulnerability in Apple Safari 3.0.2 for Windows. Attackers exploit JavaScript that overwrites the document variable and statically sets the document.domain attribute to a file:// location, allowing access to restricted information from other domains.

MitigationUpgrade from Safari 3.0.2 to a newer supported version, as this older version is no longer maintained and contains known Same Origin Policy bypass vulnerabilities.

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:= 3.0.2

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

AV:N/AC:L/Au:N/C:C/I:P/A:N

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 Safari is installed
    On Windows, check for Safari in Program Files (usually C:\Program Files\Safari or C:\Program Files (x86)\Safari) or look for Safari.exe. You can also use Control Panel > Programs and Features to list installed applications.
    Affected if Safari is not installed on the system
  2. Determine Safari version number
    Open Safari and go to the Help menu, then select 'About Safari' to display the exact version number. Alternatively, right-click on the Safari.exe file in Program Files, select Properties, and view the Details tab for the file version.
    Affected if The displayed version is exactly 3.0.2
  3. Confirm Windows platform
    Verify the operating system is Windows by right-clicking on This PC or My Computer and selecting Properties, or by running 'systeminfo' in Command Prompt.
    Affected if The system is running Windows with Safari 3.0.2 installed

You are affected if Safari version 3.0.2 is installed on a Windows system.

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

Upgrade from Safari 3.0.2 to a newer supported version, as this older version is no longer maintained and contains known Same Origin Policy bypass vulnerabilities.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.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-3514 — 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-3514 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