Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2014-3199
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 · uneditedThe wrap function in bindings/core/v8/custom/V8EventCustom.cpp in the V8 bindings in Blink, as used in Google Chrome before 38.0.2125.101, has an erroneous fallback outcome for wrapper-selection failures, which allows remote attackers to cause a denial of service via vectors that trigger stopping a worker process that had been handling an Event object.
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 confidenceA denial of service vulnerability in Google Chrome versions before 38.0.2125.101 exists in the V8 JavaScript engine's Blink bindings. The wrap function in V8EventCustom.cpp has an incorrect fallback behavior when wrapper-selection fails, allowing remote attackers to trigger a denial of service by stopping a worker process that was handling an Event object.
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
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
ChromeWeb browser
<= 38.0.2125.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome version on WindowsOpen Chrome, click the menu icon (three dots) > Help > About Google Chrome. The version number is displayed on this page.Affected if The displayed version is 38.0.2125.7 or earlier (any version up to and including 38.0.2125.7).
-
Check Google Chrome version via command line on LinuxOpen a terminal and run: google-chrome --version or chrome --versionAffected if The reported version is 38.0.2125.7 or earlier.
-
Check Chromium version on Linux systemsOpen a terminal and run: chromium --version or rpm -q chromiumAffected if The reported version is 38.0.2125.7 or earlier.
-
Check Chrome bundled with Red Hat Enterprise Linux SupplementaryOn RHEL systems with supplementary repositories enabled, run: rpm -q google-chrome or rpm -q chromeAffected if The package version shown is 38.0.2125.7-1 or earlier.
You are affected if Google Chrome or Chromium installed on your system is version 38.0.2125.7 or any earlier version, since the vulnerability was patched in version 38.0.2125.101.
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 38.0.2125.101 or later to receive the patch for this vulnerability.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3199 — 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-2014-3199 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