dbcve.org
SafariWeb browser · Apple

CVE-2010-1403

HIGH · 9.3 CVSS v2.0 Published 2010-06-11
Fix available
A fix is available. Upgrade to after 4.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
WebKit in Apple Safari before 5.0 on Mac OS X 10.5 through 10.6 and Windows, and before 4.1 on Mac OS X 10.4, accesses uninitialized memory during the handling of a use element in an SVG document, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted document containing XML that triggers a parsing error, related to ProcessInstruction.

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
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:<= 4.0.5= 4.0= 4.0.0b= 4.0.1= 4.0.2= 4.0.3= 4.0.4
WebkitWeb browser
Affected:all versions

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

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
Upgrade available Upgrade to a release after 4.0.5
Vendor patch lists.apple.com →
Recommended fix High confidence

Safari 5.0 (or Safari 4.1 for OS X 10.4)

  1. 1. Determine the current Safari version by clicking Safari > About Safari
  2. 2. For Mac OS X 10.5 through 10.6 and Windows users: Upgrade Safari to version 5.0 or later
  3. 3. For Mac OS X 10.4 users: Upgrade Safari to version 4.1 or later
  4. 4. Alternatively, ensure WebKit is updated to a version that includes the June 2010 security fixes
  5. 5. Verify the upgrade was successful by checking Safari > About Safari shows version 5.0+ (or 4.1+ for OS X 10.4)
Caveat Users on legacy Mac OS X 10.4 systems may find that Safari 4.1 is the final supported version for that platform

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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