ChromeWeb browser · Google
CVE-2011-2791
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 International Components for Unicode (ICU) functionality in Google Chrome before 13.0.782.107 allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that trigger an out-of-bounds write.
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 confidenceOut-of-bounds write vulnerability in Google Chrome's International Components for Unicode (ICU) functionality before version 13.0.782.107. Remote attackers can exploit this to cause denial of service or potentially achieve unspecified code execution via unknown vectors.
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
< 13.0.782.107CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 executable: On Windows, look in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /opt/google/chrome/google-chrome or /usr/bin/google-chromeAffected if Google Chrome browser is present on the system
-
Determine installed Chrome version on WindowsRight-click chrome.exe, select Properties, then click the Details tab and read the File version field. Alternatively, run 'chrome.exe --version' from Command Prompt or navigate to Help > About Google Chrome in the browserAffected if Version number displayed is lower than 13.0.782.107
-
Determine installed Chrome version on macOSOpen Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. Or open Chrome, go to Chrome > About Google ChromeAffected if Version number displayed is lower than 13.0.782.107
-
Determine installed Chrome version on LinuxOpen Terminal and run: google-chrome --version or /opt/google/chrome/google-chrome --versionAffected if Version number displayed is lower than 13.0.782.107
The environment is affected if Google Chrome is installed and its version is below 13.0.782.107, since the vulnerability exists in the ICU component of those versions.
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 data13.0.782.107
Update Google Chrome to version 13.0.782.107 or later. In enterprise environments, deploy the update via standard software distribution mechanisms and verify compliance.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2791 — 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-2791 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