dbcve.org
ChromeWeb browser · Google

CVE-2014-7909

MEDIUM · 5.0 CVSS v2.0 Published 2014-11-19
Fix available
A fix is available. Upgrade to after 39.0.2171.45 or later.
See remediation →
59/100
Remediation priority · Elevated
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
effects/SkDashPathEffect.cpp in Skia, as used in Google Chrome before 39.0.2171.65, computes a hash key using uninitialized integer values, which might allow remote attackers to cause a denial of service by rendering crafted data.

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

The vulnerability exists in Skia's SkDashPathEffect.cpp where uninitialized integer values are used when computing a hash key. This occurs during dash path effect processing in the graphics rendering pipeline, potentially causing unpredictable hash values and denial of service when rendering specially crafted content.

MitigationUpdate Google Chrome to version 39.0.2171.65 or later. If using Skia directly in other applications, ensure the fix for uninitialized integer usage in SkDashPathEffect is applied.

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:<= 39.0.2171.45

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

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

  1. Confirm Google Chrome is installed
    Check for Chrome executable: Windows - look for chrome.exe in Program Files, Mac - look for Google Chrome.app in Applications, Linux - run 'which google-chrome' or check /usr/bin/google-chrome
    Affected if Google Chrome is present on the system
  2. Retrieve the installed Chrome version
    Open chrome://version in the browser address bar and note the version number, or run 'google-chrome --version' from command line on Linux/Mac
    Affected if A version number is returned
  3. Compare version against affected range
    Compare the installed version number to 39.0.2171.45 - check if it is 39.0.2171.45 or earlier (less than 39.0.2171.65)
    Affected if Installed version is 39.0.2171.45 or lower, meaning the uninitialized integer vulnerability in SkDashPathEffect.cpp is present

User is affected if Google Chrome version 39.0.2171.45 or earlier is installed, as this version contains the uninitialized integer flaw in Skia's dash path effect processing.

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 a release after 39.0.2171.45
Interim mitigation

Update Google Chrome to version 39.0.2171.65 or later. If using Skia directly in other applications, ensure the fix for uninitialized integer usage in SkDashPathEffect is applied.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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