dbcve.org
BlinkApplication · Google

CVE-2011-2337

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A wrong type is used for a return value from strlen in WebKit in Google Chrome before Blink M12 on 64-bit platforms.

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 confidence

This is a type confusion vulnerability in WebKit where the return value from strlen (which returns size_t, an unsigned 64-bit type on 64-bit platforms) is incorrectly stored in a signed integer type. On 64-bit platforms, this type mismatch can cause integer overflow when processing large strings, potentially leading to heap corruption and remote code execution.

MitigationUpgrade Google Chrome to version after Blink M12 (which includes the fix) or apply vendor patches to WebKit. This is a client-side vulnerability requiring browser update.

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
BlinkApplication
Affected:< m12

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify your browser engine
    Check if you are using a WebKit or Blink-based browser (Google Chrome, Chromium, Opera, or any browser based on these projects). Look at the browser's 'About' or 'Help' section to identify the engine.
    Affected if Using any WebKit/Blink-based browser on a 64-bit platform
  2. Determine the browser version
    Open the browser and navigate to chrome://version (for Chrome/Chromium) or check 'About [Browser]' in the menu to find the full version string.
    Affected if Version is unknown or cannot be determined from the UI
  3. Check if the version is prior to Blink M12
    Compare your installed browser version against Blink M12. For Chrome, M12 corresponds to approximately version 12.x. The exact version number can be verified in the browser's version information displayed in chrome://version.
    Affected if Browser version is Chrome/Chromium 12.x or earlier, or a Blink-based browser with version tag earlier than M12
  4. Verify the platform architecture
    Check if your operating system and browser are running on a 64-bit architecture. On Windows, this can be verified in System Properties or by checking if the Program Files (x86) folder exists alongside Program Files. On macOS and Linux, run 'uname -m' in a terminal - x86_64 or amd64 indicates 64-bit.
    Affected if Running on a 64-bit platform (the integer overflow only manifests on 64-bit systems where size_t is 64-bit)
  5. Confirm JavaScript processing of large strings is possible
    The vulnerability is triggered when the browser processes JavaScript strings via the WebKit JavaScript engine. Simply having the browser process web content with JavaScript enables this attack surface. No special configuration need be enabled - the vulnerability is in the core rendering code.
    Affected if The browser processes web pages with JavaScript (which is enabled by default in all affected browsers)

You are affected if you use a WebKit/Blink-based browser (Chrome/Chromium 12.x or earlier, or any browser based on Blink versions before M12) on a 64-bit operating system and browse the web with JavaScript enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Google Chrome to version after Blink M12 (which includes the fix) or apply vendor patches to WebKit. This is a client-side vulnerability requiring browser update.

Recommended fix Moderate confidence

Blink M12 or later

  1. Upgrade Google Chrome to Blink M12 or later to resolve the strlen return type mismatch on 64-bit platforms

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

Fix this in Blink Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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