dbcve.org
SafariWeb browser · Apple

CVE-2012-3610

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, the rendering engine used by Apple Safari before version 6.0, allows remote attackers to execute arbitrary code or cause a denial of service via a crafted malicious website.

MitigationUpdate Safari to version 6.0 or later, or apply the relevant Apple security update (APPLE-SA-2012-07-25-1) to patch the WebKit vulnerability.

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. Check if Safari is installed
    On macOS, open Terminal and run: ls /Applications/ | grep -i Safari. On Windows, check C:\Program Files\Safari or C:\Program Files (x86)\Safari for the Safari folder.
    Affected if Safari is not found in the expected application directories, then Safari is not in use.
  2. Determine installed Safari version
    Open Safari, then go to Safari menu > About Safari. Alternatively, on macOS run: defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString. On Windows, right-click Safari.exe > Properties > Details tab to see the File Version.
    Affected if Unable to retrieve a version number means Safari version cannot be determined.
  3. Compare version against affected range
    Compare the retrieved version number to the affected versions: any version <= 5.1.7, or specifically 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, 1.1.1. Versions 6.0 and later are not affected.
    Affected if The installed version matches any of the listed affected versions or is less than 6.0, then the environment is vulnerable.
  4. Verify WebKit is the rendering engine
    This is inherent to Safari. The vulnerability exists in the WebKit rendering engine that Safari uses. No additional configuration check is needed.
    Affected if If using a non-WebKit browser (like Chrome which uses Chromium), this specific CVE does not apply.

If Safari is installed and the version is less than 6.0 (or matches any of the specific older versions listed), the environment is affected by this vulnerability.

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

Update Safari to version 6.0 or later, or apply the relevant Apple security update (APPLE-SA-2012-07-25-1) to patch the WebKit vulnerability.

Recommended fix High confidence

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

  1. Open Safari and go to Safari > About Safari to check the current version
  2. If running OS X Mountain Lion (10.8) or later, check for system updates via Apple menu > Software Update
  3. Install Safari 6.0 or later which contains the fixed WebKit version
  4. Alternatively, update to the latest available OS version (macOS) which includes an updated Safari with security fixes
  5. Verify the upgrade was successful by checking Safari > About Safari shows version 6.0 or higher
Caveat Safari 6.0 requires OS X Mountain Lion (10.8) or later; older Mac systems running earlier OS versions cannot upgrade to Safari 6.0 and may need to stay on older Safari versions or upgrade macOS

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
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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