CVE-2011-1300
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 · uneditedThe Program::getActiveUniformMaxLength function in libGLESv2/Program.cpp in libGLESv2.dll in the WebGLES library in Almost Native Graphics Layer Engine (ANGLE), as used in Mozilla Firefox 4.x before 4.0.1 on Windows and in the GPU process in Google Chrome before 10.0.648.205 on Windows, allows remote attackers to execute arbitrary code via unspecified vectors, related to an "off-by-three" error.
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 confidenceBuffer overflow (off-by-three error) in the Program::getActiveUniformMaxLength function in libGLESv2.dll (ANGLE WebGL library). The vulnerability allows remote code execution via malicious WebGL content in affected browsers.
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= 4.0< 10.0.648.205CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed browserCheck which web browser is installed and its exact version number. In Firefox, go to Help > About Firefox. In Chrome, go to Settings > About Chrome.Affected if The browser is either Mozilla Firefox version 4.0 or Google Chrome version earlier than 10.0.648.205
-
Verify WebGL is enabledCheck the browser settings or type 'about:config' in Firefox and search for 'webgl.enabled_for_all_sites' or in Chrome go to chrome://settings and look for WebGL settings under Advanced or Hardware Acceleration.Affected if WebGL is enabled in the browser settings, as this is required for the malicious content to trigger the vulnerability
-
Locate libGLESv2.dllSearch for the file libGLESv2.dll in the browser installation directory. In Firefox this is typically in the installation folder. In Chrome, check under the application directory.Affected if The libGLESv2.dll file from the ANGLE library is present, indicating the vulnerable component is installed
A user is affected if they are running Firefox 4.0 or Chrome versions before 10.0.648.205 with WebGL enabled, and the libGLESv2.dll (ANGLE WebGL library) is present on their system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.648.205
Update affected software to patched versions (Firefox 4.0.1+, Chrome 10.0.648.205+) or disable WebGL in browser settings as a workaround.
Firefox 4.0.1 or later; Chrome 10.0.648.205 or later
- Upgrade Mozilla Firefox 4.0 to Firefox 4.0.1 or later to resolve the libGLESv2.dll vulnerability
- For Google Chrome users on Windows, upgrade to Chrome 10.0.648.205 or later
- Both fixes address the off-by-three error in Program::getActiveUniformMaxLength function in the ANGLE library's libGLESv2/Program.cpp
- After upgrading, verify the browser version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-1300 in production — separate from our analysis above.
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.
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.
- 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