dbcve.org
SafariWeb browser · Apple

CVE-2011-1797

HIGH · 9.3 CVSS v2.0 Published 2011-07-21
Fix available
A fix is available. Upgrade to after 11.0.696.64 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 5.0.6, 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-2011-07-20-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

A memory corruption vulnerability in WebKit, the rendering engine used by Apple Safari prior to version 5.0.6, allows remote attackers to execute arbitrary code or cause a denial of service via a specially crafted website. The vulnerability stems from improper memory handling during page rendering.

MitigationUpdate Apple Safari to version 5.0.6 or later to address this vulnerability. Organizations should ensure endpoint management systems deploy browser updates across affected workstations.

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.0.5= 1.0= 1.0.0= 1.0.0b1= 1.0.0b2= 1.0.1= 1.0.2= 1.0.3= 1.1= 1.1.0= 1.1.1= 1.2
ChromiumWeb browser
Affected:<= 11.0.696.64
WebkitWeb browser
Affected:all versions

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 Safari version on Windows
    Open Safari, click Help in the menu bar, then select About Safari. The version number displays in the dialog box.
    Affected if Version is 5.0.5 or earlier, or matches any of the specific affected versions listed (1.0, 1.0.0, 1.0.0b1, 1.0.0b2, 1.0.1, 1.0.2, 1.0.3, 1.1, 1.1.0, 1.1.1, 1.2)
  2. Check Safari version on macOS
    Open Safari, then select Safari > About Safari. The version displays next to the Safari icon.
    Affected if Version is 5.0.5 or earlier, or matches any of the specific affected versions listed
  3. Check Chromium browser version
    Open Chromium, navigate to chrome://version or chromium://version, and look at the Version line.
    Affected if Version is 11.0.696.64 or earlier
  4. Check for WebKit-based applications using the vulnerable engine
    Identify any applications that use WebKit as a rendering engine (such as older browsers or custom applications). Check their documentation or binary resources for the WebKit version they embed.
    Affected if The application embeds an unpatched version of WebKit (any version prior to the fix)
  5. Check Windows registry for Safari version
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Apple\Safari\Version. Read the Version value.
    Affected if The installed version value is 5.0.5 or lower

A user is affected if they run Safari 5.0.5 or earlier, Chromium 11.0.696.64 or earlier, or any application that embeds an unpatched WebKit rendering engine.

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 11.0.696.64
Interim mitigation

Update Apple Safari to version 5.0.6 or later to address this vulnerability. Organizations should ensure endpoint management systems deploy browser updates across affected workstations.

Recommended fix High confidence

Safari 5.0.6 or later; Chromium 12 or later; WebKit post-July 2011 releases

  1. Upgrade Apple Safari to version 5.0.6 or later (or migrate to a newer supported Safari version if on legacy system)
  2. If using Chromium-based browsers, upgrade to a version newer than 11.0.696.64 (Chromium 12 or later)
  3. For WebKit-based applications, ensure WebKit is updated to a version released after the vulnerability disclosure (post-July 2011)
  4. After updating, verify the browser/application version to confirm the fix is applied
Caveat Safari 5.0.6 is a legacy version for older Mac OS X systems (Snow Leopard and earlier); some older systems may not support newer Safari versions

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA1.0 h
13.0 hours of engineering $2,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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