dbcve.org
ChromeWeb browser · Google

CVE-2011-3102

MEDIUM · 6.8 CVSS v2.0 Published 2012-05-16
Fix available
A fix is available. Upgrade to after 19.0.1084.45 or later.
See remediation →
77/100
Remediation priority · High
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
Off-by-one error in libxml2, as used in Google Chrome before 19.0.1084.46 and other products, allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via unknown vectors.

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 · moderate confidence

Off-by-one error in libxml2 library allows remote attackers to cause out-of-bounds write leading to denial of service, with possible unspecified other impact via unknown vectors involving malformed XML parsing.

MitigationUpdate libxml2 to patched version or upgrade affected Google Chrome to 19.0.1084.46 or later. Validate XML parsing functionality after patching.

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:<= 19.0.1084.45
Iphone OsOperating system
Affected:<= 6.1.4= 1.0.0= 1.0.1= 1.0.2= 1.1.0= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 2.0= 2.0.0

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Google Chrome version
    Open Chrome, click the menu icon (three dots) > Help > About Google Chrome. The version number displays next to 'Google Chrome'. On Linux, run 'google-chrome --version' or 'chromium --version' in terminal. On Windows, check 'C:\Program Files\Google\Chrome\Application\chrome.exe' properties or via Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome\DisplayVersion
    Affected if Version number is 19.0.1084.45 or lower (any version up to and including 19.0.1084.45)
  2. Identify applications using libxml2 library
    On Linux, run 'ldd /path/to/application | grep libxml' or check /usr/lib/libxml*.so files. On Windows, use a dependency walker tool or search for libxml2.dll in application directories. Search for 'libxml2' in installed program files.
    Affected if Any application linked against libxml2 is present and parses untrusted XML content
  3. Verify XML parsing usage in browsers and applications
    Review browser settings or extensions that process XML (RSS readers, XML validators, developer tools). Check if any locally installed software automatically parses XML from untrusted sources.
    Affected if Browser or application is configured to parse or render XML from external or untrusted sources
  4. Check Apple iOS version on affected devices
    On iPhone/iPad, go to Settings > General > About > Version. Compare against the listed affected versions: 6.1.4, 1.0.0 through 1.1.5, 2.0, 2.0.0.
    Affected if iOS version exactly matches one of the listed versions (1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 2.0, 2.0.0, or 6.1.4)

You are affected if Chrome version is 19.0.1084.45 or lower, or if your iOS version matches any of the specific versions listed, AND the browser or application processes XML content from potentially untrusted sources.

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.

From vendor data
Upgrade available Upgrade to a release after 19.0.1084.45
Interim mitigation

Update libxml2 to patched version or upgrade affected Google Chrome to 19.0.1084.46 or later. Validate XML parsing functionality after patching.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
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,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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