ChromeWeb browser · Google
CVE-2011-3105
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 · uneditedUse-after-free vulnerability in the Cascading Style Sheets (CSS) implementation in Google Chrome before 19.0.1084.52 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the :first-letter pseudo-element.
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 confidenceUse-after-free vulnerability in Google Chrome's CSS implementation allows remote attackers to cause denial of service or possibly execute arbitrary code via vectors related to the :first-letter pseudo-element. The flaw exists in versions before 19.0.1084.52.
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
- 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.
-
Check if Google Chrome is installedOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' from command lineAffected if Google Chrome is not installed on the system
-
Determine the installed Chrome versionOn the chrome://settings/help page, look at the version number displayed (e.g., 19.0.1084.51, 19.0.1030.0)Affected if The displayed version matches one of the affected versions: any version <= 19.0.1084.51, or exactly 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
-
Identify if :first-letter CSS pseudo-element is in useSearch project source code, web applications, or user-generated content for the ':first-letter' CSS selector patternAffected if The :first-letter pseudo-element is actively used in any CSS files or inline styles within the environment
-
Review Chrome's renderer process behaviorMonitor Chrome for crashes related to CSS rendering using chrome://crashes or system event logs, particularly when loading pages with :first-letter styled contentAffected if Unexpected crashes occur when rendering pages containing :first-letter CSS rules
You are affected if Chrome version 19.0.1084.51 or lower, or any of the specific versions from 19.0.1028.0 through 19.0.1036.3, is installed and the :first-letter CSS pseudo-element is used in your environment.
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 remediate this vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3105 — 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-3105 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