ChromeWeb browser · Google

CVE-2013-2877

MEDIUM · 5.0 CVSS v2.0 Published 2013-07-10

Fix available

A fix is available. Upgrade to after 28.0.1500.70 or later.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

parser.c in libxml2 before 2.9.0, as used in Google Chrome before 28.0.1500.71 and other products, allows remote attackers to cause a denial of service (out-of-bounds read) via a document that ends abruptly, related to the lack of certain checks for the XML_PARSER_EOF state.

Technical summary

dbcve analysis · high confidence

libxml2 before 2.9.0 contains an out-of-bounds read vulnerability in parser.c. When processing XML documents that end abruptly without proper termination, the parser fails to adequately check the XML_PARSER_EOF state, causing an out-of-bounds memory read that leads to denial of service.

MitigationUpgrade libxml2 to version 2.9.0 or later. For Google Chrome users, update to version 28.0.1500.71 or later to incorporate the patched libxml2 library.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:<= 28.0.1500.70= 28.0.1500.0= 28.0.1500.2= 28.0.1500.3= 28.0.1500.4= 28.0.1500.5= 28.0.1500.6= 28.0.1500.8= 28.0.1500.9= 28.0.1500.10= 28.0.1500.11= 28.0.1500.12

Libxml2Framework / library

Affected:<= 2.9.0= 1.7.0= 1.7.1= 1.7.2= 1.7.3= 1.7.4= 1.8.0= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: None
Availability: Partial

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed libxml2 version

Run `xml2 --version` or `xmllint --version` on Linux; on Windows check the DLL version of libxml2.dll in the application directory or system folder

Affected if The version is 2.9.0 or earlier, or specifically 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, or 1.8.5
Check installed Google Chrome version

Run `google-chrome --version` from command line, or navigate to chrome://version in the browser address bar

Affected if The version is 28.0.1500.70 or earlier, or matches any of these specific versions: 28.0.1500.0, 28.0.1500.2, 28.0.1500.3, 28.0.1500.4, 28.0.1500.5, 28.0.1500.6, 28.0.1500.8, 28.0.1500.9, 28.0.1500.10, 28.0.1500.11, or 28.0.1500.12
Identify applications using libxml2

Check which applications on the system link to libxml2 by running `ldd` on Linux binaries or examining dependency walkers on Windows; look for libxml2.dll or libxml2.so in application directories

Affected if Any application that processes XML input uses a vulnerable libxml2 version and parses untrusted XML documents

You are affected if libxml2 version is 2.9.0 or earlier (or one of the listed 1.7.x/1.8.x versions) OR Chrome version is 28.0.1500.70 or earlier, and the affected software parses XML documents.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 28.0.1500.70

Interim mitigation

Upgrade libxml2 to version 2.9.0 or later. For Google Chrome users, update to version 28.0.1500.71 or later to incorporate the patched libxml2 library.

Fix this in Chrome 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-2013-2877 — 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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2877 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-2877?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 28.0.1500.70 or later

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 5.0%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 5 hrs · Low

Typical engagement from $860

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2013-2877 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References