CVE-2014-3195 - CVE House
Back to Database
Status published Medium CVE-2014-3195

Google V8, as used in Google Chrome before 38.0.2125.101, does...

Vulnerability Description

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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2014-3195

Credits & Attribution

No credits recorded in the NVD database.

References

More from google

View All →
CVE-2025-24959
Environment Variable Injection for dotenv API in zx
Low 1
CVE-2024-45601
Local file Inclusion via static file serving functionality in Mesop
High 7.5
CVE-2022-3708
Web Stories <= 1.24.0 - Server Side Request Forgery
Critical 9.6
CVE-2022-31055
Improper Access Control in kctf
High 7.5
CVE-2022-23569
`CHECK`-fails when building invalid tensor shapes in Tensorflow
Medium 6.5

Affected Vendor

Affected Software

chrome, enterprise linux desktop supplementary, enterprise linux server supplementary, enterprise linux server supplementary eus, enterprise linux workstation supplementary
Vulnerable Versions:
0, 6.0, 6.6.z

Timeline

Official Publish: October 8th, 2014
Last Modified: August 6th, 2024
Added to House: July 19th, 2026

CVSS Vectors

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.