dbcve.org
ChromeWeb browser · Google

CVE-2010-3116

HIGH · 10.0 CVSS v2.0 Published 2010-08-24
Fix available
A fix is available. Upgrade to 1.2.6 / 4.1.3 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
Multiple use-after-free vulnerabilities in WebKit, as used in Apple Safari before 4.1.3 and 5.0.x before 5.0.3, Google Chrome before 5.0.375.127, and webkitgtk before 1.2.6, allow remote attackers to execute arbitrary code or cause a denial of service (application crash) via vectors related to improper handling of MIME types by plug-ins.

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

Multiple use-after-free vulnerabilities in WebKit's plug-in MIME type handling allow remote attackers to execute arbitrary code or cause denial of service by triggering improper memory deallocation when processing specific MIME types.

MitigationApply vendor patches by updating Safari to 4.1.3/5.0.3+, Chrome to 5.0.375.127+, or webkitgtk to 1.2.6+ across all affected systems.

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
ChromeWeb browser
Affected:< 5.0.375.127
SafariWeb browser
Affected:< 4.1.3>= 5.0, < 5.0.3
Ubuntu LinuxOperating system
Affected:= 9.10= 10.04= 10.10
Iphone OsOperating system
Affected:< 4.2
WebkitgtkWeb browser
Affected:< 1.2.6

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 the WebKit-based browser or application in use
    Determine if the system runs Google Chrome, Apple Safari, or an application using WebKitGTK (such as Midori, Epiphany, or custom applications). Check installed packages via package manager or review installed applications.
    Affected if Any Google Chrome, Apple Safari, or WebKitGTK-based application is installed on the system
  2. Check Google Chrome version
    Open chrome://version in the Chrome address bar or run 'google-chrome --version' from command line. Record the full version number.
    Affected if Chrome version is earlier than 5.0.375.127
  3. Check Apple Safari version
    Click Safari > About Safari on macOS or help menu on Windows. On iOS, go to Settings > General > About. Record the version number.
    Affected if Safari version is earlier than 4.1.3, or between 5.0.0 and 5.0.2 (inclusive)
  4. Check WebKitGTK library version
    Run 'dpkg -l libwebkit-1.0-2' on Debian/Ubuntu or check the library file version with 'ldd --version' or review the installed webkit package version via package manager.
    Affected if WebKitGTK version is earlier than 1.2.6
  5. Verify plug-in/MIME type handling is enabled
    Check that browser plug-ins or MIME type handlers are enabled in the browser settings. For Chrome: check chrome://plugins. For Safari: check Preferences > Security > Plug-in Settings. For WebKitGTK apps: verify plug-in support is not disabled.
    Affected if Browser plug-ins and MIME type handling are enabled (this is the default state in affected versions)

A system is affected if it runs any vulnerable version of Chrome (<5.0.375.127), Safari (<4.1.3 or >=5.0 <5.0.3), or WebKitGTK (<1.2.6) with plug-in/MIME type handling enabled.

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 1.2.6 / 4.1.3 / 4.2 or later
Fixed in 1.2.64.1.34.2
Interim mitigation

Apply vendor patches by updating Safari to 4.1.3/5.0.3+, Chrome to 5.0.375.127+, or webkitgtk to 1.2.6+ across all affected systems.

Recommended fix High confidence

Chrome 5.0.375.127 / Safari 4.1.3 or 5.0.3 / Webkitgtk 1.2.6 / iOS 4.2

  1. Identify the currently installed browser or WebKit library version
  2. For Google Chrome: Upgrade to version 5.0.375.127 or later
  3. For Apple Safari: Upgrade to version 4.1.3 or 5.0.3 or later (depending on your OS version)
  4. For Webkitgtk: Upgrade to version 1.2.6 or later
  5. For Ubuntu Linux systems: Apply security updates via 'sudo apt-get update && sudo apt-get upgrade' to receive the fixed WebKit packages
  6. For iPhone OS: Upgrade to iOS 4.2 or later
  7. Restart the browser after applying updates
Caveat These are security patch releases; minimal compatibility issues expected but older plugins may require updates

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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