SafariWeb browser · Apple
CVE-2012-3609
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 · moderate confidenceMemory corruption vulnerability in WebKit (Safari's rendering engine) allows remote attackers to execute arbitrary code or cause a denial of service via a crafted website. The vulnerability affects 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 versionOn Mac: Open Safari and select Safari > About Safari. On Windows: Open Safari and select Help > About Safari. Note the full version number displayed.Affected if The displayed version is earlier than 6.0 (for example 5.1.7, 5.1.6, 5.0.x, or any version 1.x listed in the affected range).
-
Verify WebKit engine version (optional)In Safari, open the Web Inspector (Develop > Show Web Inspector or press Option+Command+I). Look for the WebKit version information typically shown in the console or navigator panel.Affected if The WebKit version corresponds to an unpatched build predating the Safari 6.0 release.
-
Confirm OS platform supports Safari 6.0Note that Safari 6.0 was released only for Mac OS X (Lion and later) and was not available for Windows. Check your operating system version.Affected if Running Windows, or a Mac OS version earlier than Lion, means Safari 6.0 is unavailable and the vulnerable WebKit component remains unpatched.
You are affected if Safari is installed at any version earlier than 6.0, as listed in the affected versions range, and you use the WebKit rendering engine to browse the web.
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 to obtain the patched WebKit component. Organizations should deploy the update through their patch management infrastructure.
Safari 6.0 or later
- 1. Back up your current browser bookmarks, passwords, and preferences
- 2. Check your current macOS version (Apple menu > About This Mac)
- 3. If running macOS 10.7 (Lion) or earlier, upgrade to macOS 10.8 (Mountain Lion) or later to support Safari 6.0
- 4. Open the Mac App Store
- 5. Search for "Safari" or check for system updates
- 6. Download and install Safari 6.0 or later
- 7. After installation, verify the version by going to Safari > About Safari
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3609 — 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-3609 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