dbcve.org
ChromeWeb browser · Google

CVE-2014-3195

MEDIUM · 5.0 CVSS v2.0 Published 2014-10-08
Fix available
A fix is available. Upgrade to after 38.0.2125.7 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
Google V8, as used in Google Chrome before 38.0.2125.101, does not properly track JavaScript heap-memory allocations as allocations of uninitialized memory and does not properly concatenate arrays of double-precision floating-point numbers, which allows remote attackers to obtain sensitive information via crafted JavaScript code, related to the PagedSpace::AllocateRaw and NewSpace::AllocateRaw functions in heap/spaces-inl.h, the LargeObjectSpace::AllocateRaw function in heap/spaces.cc, and the Runtime_ArrayConcat function in runtime.cc.

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

A memory management flaw in Google V8 JavaScript engine versions before 38.0.2125.101 causes improper tracking of heap-memory allocations, resulting in exposure of uninitialized memory contents. Additionally, the Runtime_ArrayConcat function fails to properly handle concatenation of double-precision floating-point arrays, leaking sensitive heap data to JavaScript code.

MitigationUpdate Google Chrome to version 38.0.2125.101 or later, or update the V8 engine in affected Node.js/embedded applications to a patched version that properly initializes allocated memory and validates array concatenation operations.

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:<= 38.0.2125.7
Enterprise Linux Desktop SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server Supplementary EusOperating system
Affected:= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
Affected:= 6.0

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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. Check Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal to display the installed Chrome version
    Affected if Version is 38.0.2125.7 or earlier (any version up to and including 38.0.2125.7)
  2. Check V8 engine version in Node.js
    Run 'node -e "console.log(process.versions.v8)"' to output the V8 engine version bundled with Node.js
    Affected if V8 version is below 38.0.2125.101 (compare your version number to this baseline)
  3. Verify Chrome installation on Red Hat systems
    On RHEL 6.x systems, query the installed Chrome package using 'rpm -q google-chrome' or check the version via 'rpm -q --info google-chrome'
    Affected if Google Chrome is installed and the package version is 38.0.2125.7-1 or earlier
  4. Identify embedded applications using vulnerable V8
    Locate any standalone applications that bundle the V8 engine (check for libv8.so or v8.dll files) and query their embedded V8 version through application flags or binary inspection
    Affected if The bundled V8 version is prior to 38.0.2125.101

You are affected if Chrome version is 38.0.2125.7 or earlier, or any application (including Node.js) is running a V8 engine version below 38.0.2125.101.

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 38.0.2125.7
Interim mitigation

Update Google Chrome to version 38.0.2125.101 or later, or update the V8 engine in affected Node.js/embedded applications to a patched version that properly initializes allocated memory and validates array concatenation operations.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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