dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-2901

HIGH · 7.5 CVSS v2.0 Published 2013-08-21
Fix available
A fix is available. Upgrade to after 29.0.1547.56 or later.
See remediation →
84/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
Multiple integer overflows in (1) libGLESv2/renderer/Renderer9.cpp and (2) libGLESv2/renderer/Renderer11.cpp in Almost Native Graphics Layer Engine (ANGLE), as used in Google Chrome before 29.0.1547.57, allow remote attackers to cause a denial of service 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 · high confidence

Integer overflow vulnerabilities in libGLESv2/renderer (Renderer9.cpp and Renderer11.cpp) in the ANGLE graphics library used by Google Chrome allow remote attackers to cause denial of service or potentially achieve unspecified impact via malicious graphics operations. These overflows occur during graphics rendering calculations and could corrupt memory or cause unexpected behavior.

MitigationUpdate Google Chrome to version 29.0.1547.57 or later to incorporate the patched ANGLE library. For embedded applications using ANGLE directly, update to a version containing the integer overflow fixes in the renderer components.

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
Debian LinuxOperating system
Affected:= 7.0
ChromeWeb browser
Affected:<= 29.0.1547.56= 29.0.1547.0= 29.0.1547.1= 29.0.1547.2= 29.0.1547.3= 29.0.1547.4= 29.0.1547.5= 29.0.1547.7= 29.0.1547.8= 29.0.1547.9= 29.0.1547.10= 29.0.1547.11

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

AV:N/AC:L/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, go to chrome://settings/help, or run 'google-chrome --version' from command line
    Affected if Version is 29.0.1547.56 or earlier, or falls between 29.0.1547.0 and 29.0.1547.11 inclusive
  2. Verify ANGLE library (libGLESv2) presence on Debian
    Run 'dpkg -l | grep libgles' or 'apt list --installed 2>/dev/null | grep -i libgles' to list installed OpenGL ES library packages
    Affected if Package libgles2 or libglesv2 (or similar ANGLE-related package) is installed on Debian 7.0
  3. Confirm Chrome uses ANGLE graphics backend
    Navigate to chrome://gpu in Chrome and look for ' ANGLE ' in the Graphics Feature Status section, or check for presence of libGLESv2.dll (Windows) or libGLESv2.so (Linux) in the Chrome installation directory
    Affected if ANGLE is listed as the WebGL renderer; the vulnerable libGLESv2/renderer code is active
  4. Check Chrome binary for linked ANGLE library version
    On Linux, run 'ldd /opt/google/chrome/chrome | grep -i angle' or 'strings /opt/google/chrome/lib/libGLESv2.so | grep -i version' if accessible
    Affected if The linked libGLESv2 library corresponds to an affected Chrome version (29.x branch before 29.0.1547.57)

A user is affected if they are running Google Chrome version 29.0.1547.56 or earlier, or any version from 29.0.1547.0 through 29.0.1547.11, with ANGLE/WebGL enabled as the graphics backend.

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

Update Google Chrome to version 29.0.1547.57 or later to incorporate the patched ANGLE library. For embedded applications using ANGLE directly, update to a version containing the integer overflow fixes in the renderer components.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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