dbcve.org
ChromeWeb browser · Google

CVE-2014-1731

HIGH · 7.5 CVSS v2.0 Published 2014-04-26
Fix available
A fix is available. Upgrade to 34.0.1847.131 / 34.0.1847.132 or later.
See remediation →
84/100
Remediation priority · High
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
core/html/HTMLSelectElement.cpp in the DOM implementation in Blink, as used in Google Chrome before 34.0.1847.131 on Windows and OS X and before 34.0.1847.132 on Linux, does not properly check renderer state upon a focus event, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage "type confusion" for SELECT elements.

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 confidence

Type confusion vulnerability in Blink's HTMLSelectElement implementation allows attackers to manipulate SELECT element focus events to cause denial of service or potentially execute arbitrary code via renderer state confusion.

MitigationUpdate Google Chrome to version 34.0.1847.131 or later on Windows/OS X, and 34.0.1847.132 or later on Linux.

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
Affected:< 34.0.1847.131< 34.0.1847.132

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Google Chrome is installed
    Check for Chrome in the system: On Windows, look for Google Chrome in Program Files or via the Start menu. On macOS, check /Applications for Google Chrome. On Linux, run 'which google-chrome' or 'which chromium-browser' in terminal.
    Affected if Google Chrome is present on the system
  2. Find installed Chrome version
    Open Google Chrome, click the menu icon (three dots) in the top right, select Help, then select About Google Chrome. The version number is displayed on this page.
    Affected if Cannot determine the version (Chrome not launching or corrupted install)
  3. Compare version to affected ranges
    Note the version number displayed in the About page. Compare it: For Windows or macOS, check if version is less than 34.0.1847.131. For Linux, check if version is less than 34.0.1847.132.
    Affected if Installed version is below 34.0.1847.131 on Windows/OS X, or below 34.0.1847.132 on Linux

The user is affected if Google Chrome is installed and its version number is lower than 34.0.1847.131 (Windows/OS X) or 34.0.1847.132 (Linux).

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.

From vendor data
Upgrade available Upgrade to 34.0.1847.131 / 34.0.1847.132 or later
Fixed in 34.0.1847.13134.0.1847.132
Interim mitigation

Update Google Chrome to version 34.0.1847.131 or later on Windows/OS X, and 34.0.1847.132 or later on Linux.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

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