dbcve.org
ChromeWeb browser · Google

CVE-2011-3099

HIGH · 10.0 CVSS v2.0 Published 2012-05-16
Fix available
A fix is available. Upgrade to after 19.0.1084.45 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Use-after-free vulnerability in the PDF functionality in Google Chrome before 19.0.1084.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving a malformed name for the font encoding.

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

A use-after-free vulnerability in Google Chrome's PDF functionality allows remote attackers to execute arbitrary code or cause denial of service by tricking users into opening PDFs with malformed font encoding names, leading to memory corruption after a freed object is accessed.

MitigationUpdate Google Chrome to version 19.0.1084.46 or later to patch the vulnerability. Avoid opening untrusted PDF files until the browser is updated.

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

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
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 checks

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

  1. Check installed Chrome version
    Navigate to chrome://settings/help or click Menu > Help > About Google Chrome to view the current version number
    Affected if The displayed version is 19.0.1084.45 or earlier
  2. Verify PDF viewer is enabled
    Navigate to chrome://plugins and look for 'Chrome PDF Viewer' or go to chrome://settings and check 'PDF documents' settings
    Affected if The Chrome PDF Viewer plugin is enabled (it is enabled by default in affected versions)
  3. Assess PDF exposure risk
    Determine if the user commonly opens PDF files from untrusted or external sources using Chrome's built-in PDF viewer
    Affected if Users open PDF files in Chrome, particularly from email attachments or untrusted websites

The user is affected if Chrome version is 19.0.1084.45 or earlier and they use Chrome's built-in PDF viewer to open PDF files.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 19.0.1084.45
Interim mitigation

Update Google Chrome to version 19.0.1084.46 or later to patch the vulnerability. Avoid opening untrusted PDF files until the browser is updated.

Recommended fix High confidence

19.0.1084.46

  1. 1. Open Google Chrome browser
  2. 2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
  3. 3. The About Chrome page will display the current version and check for updates
  4. 4. If an update is available, click 'Update Google Chrome'
  5. 5. Restart the browser to apply the update
  6. 6. Verify the version is 19.0.1084.46 or later by returning to Help > About Google Chrome

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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