First published: Wed Oct 08 2014(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome | <=38.0.2125.7 | |
redhat enterprise linux desktop supplementary | =6.0 | |
Red Hat Enterprise Linux Server Supplementary | =6.0 | |
Red Hat Enterprise Linux Server Supplementary EUS | =6.6.z | |
Red Hat Enterprise Linux Workstation Supplementary | =6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-3195 has been classified as a medium severity vulnerability.
To fix CVE-2014-3195, update your Google Chrome to version 38.0.2125.101 or later.
CVE-2014-3195 affects Google Chrome versions before 38.0.2125.101.
CVE-2014-3195 allows remote attackers to obtain sensitive information due to improper memory handling.
Yes, CVE-2014-3195 relates to the improper tracking of JavaScript heap-memory allocations.