dbcve.org
ChromeWeb browser · Google

CVE-2011-2839

HIGH · 7.5 CVSS v2.0 Published 2011-08-29
Fix available
A fix is available. Upgrade to 13.0.782.215 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
The PDF implementation in Google Chrome before 13.0.782.215 on Linux does not properly use the memset library function, which allows 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 · moderate confidence

Google Chrome before version 13.0.782.215 on Linux contains a vulnerability in its PDF implementation where the memset library function is used incorrectly, leading to potential denial of service or unspecified remote code execution via unknown attack vectors.

MitigationUpdate Google Chrome on Linux to version 13.0.782.215 or later to patch the improper memset usage in the PDF rendering component.

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:< 13.0.782.215

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. Verify Google Chrome is installed on Linux
    Run 'which google-chrome' or 'which chromium' in the terminal to locate the Chrome executable
    Affected if Chrome executable is not found on the system
  2. Determine the installed Google Chrome version
    Execute 'google-chrome --version' or 'chromium --version' in the terminal to retrieve the version number
    Affected if Version command fails or returns no output
  3. Compare version against the vulnerable threshold
    Compare the installed version number to 13.0.782.215 - any version lower than 13.0.782.215 is within the vulnerable range
    Affected if Installed version is less than 13.0.782.215
  4. Confirm PDF rendering capability is in use
    The flaw is in Chrome's PDF rendering component - the built-in PDF viewer is enabled by default and can be triggered by opening any PDF file in the browser
    Affected if Users can open and view PDF files within Chrome

A Linux system is affected if Google Chrome version is below 13.0.782.215 and the built-in PDF viewer is used to render PDF documents

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 13.0.782.215 or later
Fixed in 13.0.782.215
Interim mitigation

Update Google Chrome on Linux to version 13.0.782.215 or later to patch the improper memset usage in the PDF rendering component.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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