ChromeWeb browser · Google
CVE-2011-3922
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 · uneditedStack-based buffer overflow in Google Chrome before 16.0.912.75 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to glyph handling.
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 confidenceStack-based buffer overflow vulnerability in Google Chrome's glyph (font rendering) handling code, affecting versions prior to 16.0.912.75. Attackers can trigger the overflow via malicious web pages containing specially crafted font/glyph data, potentially leading to code execution or denial of service.
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
< 16.0.912.75CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for chrome.exe on Windows (typically in C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\), or google-chrome/chromium binary on Linux (check /usr/bin/google-chrome or /usr/bin/chromium), or Google Chrome.app on macOS (check /Applications/Google Chrome.app/Contents/MacOS/)Affected if Google Chrome is not found on the system, this CVE does not apply
-
Determine installed Chrome versionOpen Google Chrome, click the menu icon (three dots), select Help, then About Google Chrome. Alternatively, run 'chrome --version' from command line on Linux, or right-click the Chrome shortcut and select Properties on Windows to view the version in the Target fieldAffected if The displayed version number is less than 16.0.912.75 (for example, 16.0.912.74, 16.0.912.x versions below .75, or any earlier major version like 15.x, 14.x, etc.)
-
Confirm vulnerability trigger conditionThis vulnerability is triggered when processing malicious font/glyph data in web pages. No special configuration needs to be checked - any use of Chrome to browse web pages exposes the user if the version is vulnerableAffected if The browser is used to render web content and the installed version is below 16.0.912.75
A user is affected if Google Chrome is installed with a version number lower than 16.0.912.75 and the browser is used to render web pages containing potentially malicious font/glyph data.
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.
From vendor data16.0.912.75
Update Google Chrome to version 16.0.912.75 or later to obtain the patched version of the font rendering component.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2011-3922 — 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-3922 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