ChromeWeb browser · Google
CVE-2011-3104
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 · uneditedSkia, as used in Google Chrome before 19.0.1084.52, allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified 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 · high confidenceAn out-of-bounds read vulnerability exists in the Skia graphics library embedded in Google Chrome versions prior to 19.0.1084.52. Attackers can trigger this flaw through unspecified vectors to cause a denial of service via memory access beyond allocated buffer boundaries.
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
<= 19.0.1084.51= 19.0.1028.0= 19.0.1029.0= 19.0.1030.0= 19.0.1031.0= 19.0.1032.0= 19.0.1033.0= 19.0.1034.0= 19.0.1035.0= 19.0.1036.0= 19.0.1036.2= 19.0.1036.3CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Determine installed Google Chrome versionOpen Chrome and navigate to chrome://version, or run from command line: 'google-chrome --version' on Linux, 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' on Windows, or 'open -a "Google Chrome" --args --version' on macOSAffected if The displayed version is <= 19.0.1084.51 OR equals any of: 19.0.1028.0, 19.0.1029.0, 19.0.1030.0, 19.0.1031.0, 19.0.1032.0, 19.0.1033.0, 19.0.1034.0, 19.0.1035.0, 19.0.1036.0, 19.0.1036.2, or 19.0.1036.3
-
Confirm Skia library presenceThe Skia library is embedded within the Chrome binary and loads automatically. Verify Chrome is installed by checking for the executable in standard installation paths: /usr/bin/google-chrome on Linux, C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, or /Applications/Google Chrome.app on macOSAffected if If Chrome is installed, the Skia library is present and active, making the vulnerability applicable if the version check above shows an affected version
-
Identify if Chrome is actively usedCheck for running Chrome processes using task manager (Windows), Activity Monitor (macOS), or 'ps aux | grep chrome' (Linux). Also check for Chrome browser shortcuts or recent browser history indicating usageAffected if Any active or recent use of an affected Chrome version means the Skia graphics library has been invoked, potentially exposing the environment to the out-of-bounds read flaw
The environment is affected if the installed Google Chrome version falls within 19.0.1028.0 through 19.0.1036.3 or is 19.0.1084.51 or lower, as these versions contain the vulnerable Skia graphics library.
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 dataUpdate Google Chrome to version 19.0.1084.52 or later to obtain the patched Skia library. In enterprise environments, deploy the update via standard software distribution mechanisms and verify the installed version.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3104 — 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-3104 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