SafariWeb browser · Apple
CVE-2012-3625
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 · uneditedWebKit, as used in Apple Safari before 6.0, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2012-07-25-1.
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 confidenceMemory corruption vulnerability in WebKit rendering engine allows remote code execution or denial of service via malicious website visits in Safari versions before 6.0.
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.1.7= 1.0= 1.0.0= 1.0.0b1= 1.0.0b2= 1.0.1= 1.0.2= 1.0.3= 1.0b1= 1.1= 1.1.0= 1.1.1CVSS 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.
-
Determine installed Safari versionOpen Safari, click Safari menu, select About Safari. The version number displays next to the Safari name.Affected if Version displayed is earlier than 6.0 (for example 5.1.7, 5.1, 5.0.x, or any 1.x version)
-
Confirm version via command lineRun command: /Applications/Safari.app/Contents/MacOS/Safari --version or check system_profiler SPApplicationsDataType for Safari version.Affected if Reported version is below 6.0
-
Identify WebKit version (optional)In Safari, go to Develop menu > User Agent to view string which often contains WebKit version number.Affected if WebKit version corresponds to the 1.0.x series (1.0, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0b1, 1.1, 1.1.0, 1.1.1)
-
Verify affected platformConfirm the system is running OS X or a platform where this Safari version is installed. This vulnerability affects Safari on OS X.Affected if Running Safari 5.1.7 or earlier on OS X
User is affected if Safari version is 5.1.7 or any earlier version (including the 1.x WebKit-based Safari releases), since the vulnerability exists in versions before 6.0.
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 · scopedUpdate Safari to version 6.0 or later which contains the patched WebKit component; alternatively disable or restrict Safari usage until the update can be deployed.
Safari 6.0 or later (preferably latest available version for your OS)
- Verify current Safari version by selecting Safari > About Safari
- Back up bookmarks, passwords, and any critical browser data
- Upgrade to Safari 6.0 or later. For macOS users: use Software Update (Apple menu > Software Update) or download from Apple.com. For Windows users: download Safari 6.0 from Apple's support website
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
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3625 — 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-2012-3625 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