dbcve.org
SafariWeb browser · Apple

CVE-2012-3618

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 versions before 6.0. Attackers can exploit this by tricking users into visiting crafted malicious websites, leading to arbitrary code execution or denial of service through memory corruption and application crashes.

MitigationUpdate Apple Safari to version 6.0 or later to obtain the patched WebKit component. Organizations should deploy this update across all affected endpoints.

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: Click Safari > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal. On Windows: Help > About Safari in the menu.
    Affected if The displayed version is 5.1.7 or lower, or matches any of these: 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
  2. Confirm WebKit is the active rendering engine
    Safari uses WebKit by default for all page rendering. No additional configuration check is needed for this vulnerability.
    Affected if Safari is running at all (WebKit is always the rendering engine in Safari)
  3. Check for Safari updates
    Open Safari and go to Safari > Software Update (macOS) or Help > Check for Updates (Windows) to see if version 6.0 or later is available.
    Affected if An update to version 6.0 or later is available, indicating the current version is vulnerable

You are affected if Safari is installed and its version is 5.1.7 or lower, or any of the specific older versions listed (1.0 through 1.1.1), since these all contain the vulnerable WebKit component.

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 Apple Safari to version 6.0 or later to obtain the patched WebKit component. Organizations should deploy this update across all affected endpoints.

Recommended fix High confidence

Safari 6.0 or later (requires OS X 10.7.3 or later)

  1. 1. Verify current Safari version by clicking Safari > About Safari
  2. 2. If running Safari 5.1.7 or earlier, determine your macOS version (Apple menu > About This Mac)
  3. 3. For macOS 10.7.3 or later: Download and install Safari 6.0 or later from Apple Support Downloads (support.apple.com/kb/DL1572)
  4. 4. For macOS 10.6.8: Apple no longer provides Safari updates for this OS; consider upgrading macOS or using an alternative browser
  5. 5. After upgrade, verify version is 6.0 or higher via Safari > About Safari
Caveat Safari 6.0 requires OS X 10.7.3 (Lion) or later; users on OS X 10.6.8 (Snow Leopard) cannot upgrade and must use an alternative browser or upgrade macOS

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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