ChromeWeb browser · Google

CVE-2013-2914

MEDIUM · 6.8 CVSS v2.0 Published 2013-10-02

Fix available

A fix is available. Upgrade to after 30.0.1599.65 or later.

See remediation →

77/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Use-after-free vulnerability in the color-chooser dialog in Google Chrome before 30.0.1599.66 on Windows allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to color_chooser_dialog.cc and color_chooser_win.cc in browser/ui/views/.

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in the color-chooser dialog component of Google Chrome on Windows. The flaw exists in color_chooser_dialog.cc and color_chooser_win.cc files within the browser/ui/views/ directory. A remote attacker could trigger the vulnerability through malicious web content to cause denial of service or potentially achieve arbitrary code execution.

MitigationUpdate Google Chrome to version 30.0.1599.66 or later. In enterprise environments, deploy the Chrome update via standard patch management processes (e.g., group policy, SCCM, or other deployment tools).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:<= 30.0.1599.65= 30.0.1599.0= 30.0.1599.1= 30.0.1599.2= 30.0.1599.4= 30.0.1599.5= 30.0.1599.6= 30.0.1599.7= 30.0.1599.8= 30.0.1599.9= 30.0.1599.10= 30.0.1599.11

CVSS breakdown

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?

dbcve checks

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

Check if Google Chrome is installed on Windows

Open Chrome and navigate to chrome://settings/help, or check Programs and Features in Control Panel for Google Chrome entry

Affected if Google Chrome is not installed or is installed on a non-Windows platform (this CVE only affects Windows)
Determine the installed Chrome version number

In Chrome address bar, type chrome://settings/help and note the version number displayed (format: X.X.X.X)

Affected if Version is 30.0.1599.0 through 30.0.1599.65, or version is 30.0.1599.66 and above is NOT affected
Verify the exact build number within the 30.0.1599.x branch

On chrome://settings/help page, confirm the full version string (e.g., 30.0.1599.65) matches any of these specific builds: .0, .1, .2, .4, .5, .6, .7, .8, .9, .10, .11, or any version up to and including .65

Affected if The exact build matches one of the listed affected versions or is <= 30.0.1599.65
Confirm the color chooser dialog feature is accessible

The vulnerability exists in the color chooser component (browser/ui/views/color_chooser_win.cc). This dialog is invoked when a webpage uses an <input type='color'> element or similar color picker functionality

Affected if The color chooser dialog feature is present and usable in the Chrome installation

A user is affected if they are running Google Chrome for Windows with version 30.0.1599.0 through 30.0.1599.65 (or any of the specifically listed build numbers), where the color chooser dialog component is accessible.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 30.0.1599.65

Interim mitigation

Update Google Chrome to version 30.0.1599.66 or later. In enterprise environments, deploy the Chrome update via standard patch management processes (e.g., group policy, SCCM, or other deployment tools).

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2914 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-2914?

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.

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

At a glance

A fix existsUpgrade to after 30.0.1599.65 or later

Severity 6.8 Medium

Exploit likelihood EPSS, next 30 days 1.2%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2013-2914 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References