SafariWeb browser · Apple
CVE-2010-3803
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 · uneditedInteger overflow in WebKit in Apple Safari before 5.0.3 on Mac OS X 10.5 through 10.6 and Windows, and before 4.1.3 on Mac OS X 10.4, allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted string.
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 confidenceInteger overflow vulnerability in WebKit's string handling allows remote attackers to execute arbitrary code or crash the Safari browser via a crafted malicious string.
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
<= 5.0.2= 5.0= 5.0.1<= 4.1.2= 1.0= 1.0.0= 1.0.0b1= 1.0.0b2= 1.0.1= 1.0.2= 1.0.3= 1.1all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Safari version on MacOpen Safari, then click Safari > About Safari (or Help > About Safari on Windows). The version number appears in the window that opens.Affected if The version is 5.0, 5.0.1, 5.0.2 or lower; or 4.1.2 or lower; or any of 1.0, 1.0.0, 1.0.0b1, 1.0.0b2, 1.0.1, 1.0.2, 1.0.3, 1.1.
-
Check Safari version on WindowsOpen Safari, then click Help > About Safari. The version number displays in the dialog box.Affected if The version matches any of the affected Safari versions listed in the CVE (<=5.0.2, <=4.1.2, or the specific 1.x versions).
-
Check WebKit version used by SafariIn Safari, open the Inspector (Develop > Show Web Inspector) or visit a page that displays user-agent string. The WebKit version is embedded in the user-agent.Affected if The WebKit version is any version (the CVE states all WebKit versions are affected).
-
Confirm browser is used to access web contentDetermine whether Safari (or any WebKit-based browser) is actively used to browse websites.Affected if The browser is used to visit websites, as the vulnerability is triggered by loading a crafted malicious string via a web page.
You are affected if you run any Safari version 5.0.2 or lower, 4.1.2 or lower, or any 1.x version, and you use the browser to access web content.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Safari to version 5.0.3 or later (Mac OS X 10.5-10.6/Windows) or 4.1.3 or later (Mac OS X 10.4). For legacy systems no longer receiving Safari updates, consider using an alternative browser or isolating the system.
Safari 5.0.3 (or latest 5.x) for Mac OS X 10.5-10.6/Windows; Safari 4.1.3 (or latest 4.x) for Mac OS X 10.4
- Upgrade to Safari 5.0.3 or later for Mac OS X 10.5 through 10.6 and Windows systems
- Upgrade to Safari 4.1.3 or later for Mac OS X 10.4 systems
- Alternatively, update to the latest available Safari version which includes the patched WebKit component
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2010-3803 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-3803 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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