dbcve.org
SafariWeb browser · Apple

CVE-2012-3669

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

This is a memory corruption vulnerability in WebKit, the rendering engine used by Apple Safari. Attackers can exploit this by tricking users into visiting crafted malicious websites, leading to arbitrary code execution or application crash due to memory corruption during the rendering process.

MitigationUpdate Apple Safari to version 6.0 or later, which contains the patched WebKit version. Until updated, avoid browsing untrusted websites.

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. Verify Safari is installed
    Check for Safari application at /Applications/Safari.app on macOS, or search for safari.exe on Windows systems
    Affected if Safari application exists on the system
  2. Determine installed Safari version
    On macOS: click Safari > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal. On Windows: right-click Safari.exe > Properties > Details tab for version info
    Affected if Version displays as 5.1.7 or earlier, or as any of the specific versions listed: 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
  3. Confirm WebKit rendering engine is in use
    Safari uses WebKit by default for all web browsing. No additional configuration check needed - the vulnerability exists in the WebKit library bundled with affected Safari versions
    Affected if Safari is used for web browsing at all, as WebKit is the default rendering engine
  4. Verify browser can access untrusted websites
    Check if Safari has network access and is not restricted by parental controls, enterprise policies, or DNS-level blocking that would prevent visiting arbitrary websites
    Affected if Browser has unrestricted network access and could be used to visit the malicious website described in the attack vector

The user is affected if Safari is installed with a version matching <= 5.1.7 or any of the specific versions listed (1.0 through 1.1.1), and the browser can be used to visit 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

Update Apple Safari to version 6.0 or later, which contains the patched WebKit version. Until updated, avoid browsing untrusted websites.

Recommended fix High confidence

Safari 6.0 or later (note: Safari 6.0 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, close the browser
  3. 3. Open the Mac App Store (on macOS) or download Safari from Apple's official website (for supported older OS versions)
  4. 4. Install Safari 6.0 or later. On macOS, this typically requires going to the Mac App Store > Updates and installing the Safari update
  5. 5. After installation, verify the version is 6.0 or higher via Safari > About Safari
Caveat Safari 6.0 requires OS X 10.7.3 (Lion) or later; older Macs running OS X 10.6 or earlier cannot upgrade to Safari 6.0 and remain vulnerable

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-3669 — 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-3669 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