dbcve.org
SafariWeb browser · Apple

CVE-2012-3611

HIGH · 9.3 CVSS v2.0 Published 2012-07-25
Fix available
A fix is available. Upgrade to after 5.1.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
WebKit, 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 confidence

Memory corruption vulnerability in WebKit's rendering engine allows remote code execution or denial of service via maliciously crafted web pages visited in Safari versions before 6.0.

MitigationUpgrade to Safari 6.0 or later to obtain the patched WebKit version; alternatively, disable JavaScript or restrict browsing to trusted sites as a workaround.

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:<= 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.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Safari version
    On macOS: Open Safari and go to Safari > About Safari. On Windows: Open Safari and go to Help > About Safari. The version number is displayed in the dialog.
    Affected if The displayed version is 5.1.7 or lower, or any of these versions: 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, or 1.1.1. Any version before 6.0 is affected.
  2. Verify WebKit version (optional)
    In Safari, open the Web Inspector (Develop > Show Web Inspector) or visit a page like 'webkit.org' that displays browser engine information. Look for the WebKit build number.
    Affected if The WebKit version corresponds to a build released before Safari 6.0 (the patched WebKit version). This confirms the vulnerable rendering engine is in use.
  3. Confirm JavaScript is enabled
    In Safari, go to Safari > Settings > Security (or Preferences > Security). Check the 'Enable JavaScript' checkbox.
    Affected if JavaScript is enabled. The vulnerability is triggered when visiting maliciously crafted web pages, which requires JavaScript to be active.
  4. Assess exposure to untrusted web content
    Review browsing habits: determine if Safari is used to visit websites other than trusted internal or whitelisted sites.
    Affected if Safari is used to browse the open internet or untrusted websites. The flaw requires a user to visit a malicious web page to be exploited.

You are affected if Safari version is less than 6.0 AND JavaScript is enabled AND the browser is used to visit potentially untrusted websites.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.1.7
Interim mitigation

Upgrade to Safari 6.0 or later to obtain the patched WebKit version; alternatively, disable JavaScript or restrict browsing to trusted sites as a workaround.

Recommended fix High confidence

Safari 6.0 or later (included with macOS Mountain Lion 10.8 and later)

  1. Check current Safari version by selecting Safari > About Safari
  2. Determine if your Mac can run macOS Mountain Lion (10.8) or later, which includes Safari 6.0
  3. If your Mac supports it, upgrade to macOS Mountain Lion (10.8) or later via the Mac App Store or a fresh install
  4. After upgrading the OS, Safari 6.0 or later will be included and the vulnerability will be patched
  5. Alternatively, download Safari 6.0 or later directly from Apple's website if your current OS supports it
Caveat Requires upgrading to macOS Mountain Lion (10.8) or later; older Macs and legacy operating systems may not support this upgrade path

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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