dbcve.org
SafariWeb browser · Apple

CVE-2007-2398

HIGH · 7.1 CVSS v2.0 Published 2007-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 3.0.1 beta (522.12.12) on Windows allows remote attackers to modify the window title and address bar while filling the main window with arbitrary content by setting the location bar and using setTimeout() to create an event that modifies the window content, which could facilitate phishing attacks.

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

UI spoofing vulnerability in Safari 3.0.1 beta allows remote attackers to manipulate the address bar and window title while displaying arbitrary content in the main window using setTimeout() events, facilitating phishing attacks.

MitigationUpgrade Safari to a patched version beyond 3.0.1 beta; users should ensure automatic updates are enabled or manually download the latest stable Safari release.

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

AV:N/AC:M/Au:N/C:N/I:C/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 installed Safari version
    Open Safari, then go to Safari menu > About Safari. The version number will display next to the Safari logo.
    Affected if The version shown is exactly 3.0.1 (the build number may also display)
  2. Verify JavaScript is enabled
    Go to Safari > Settings > Security (or Preferences > Security on older versions) and check if 'Enable JavaScript' is checked.
    Affected if JavaScript is enabled (this is the default setting and required for the setTimeout exploit to work)
  3. Confirm the exact build number
    In About Safari, note both the version number (3.0.1) and any build number shown; some beta releases have multiple builds.
    Affected if The version displays as Safari 3.0.1 specifically

You are affected if your Safari version is exactly 3.0.1 and JavaScript is enabled, as this specific beta version contains the UI spoofing flaw via setTimeout events.

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 Safari to a patched version beyond 3.0.1 beta; users should ensure automatic updates are enabled or manually download the latest stable Safari release.

Fix this in Safari Scoped from the published advisory
  • Consultation0.5 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.3 h
1.8 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-2398 — 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-2398 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