CVE-2014-3195
Publication date 8 October 2014
Last updated 24 July 2024
Ubuntu priority
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.
Status
Package | Ubuntu Release | Status |
---|---|---|
chromium-browser | ||
18.04 LTS bionic |
Fixed 38.0.2125.111-0ubuntu1.1103
|
|
16.04 LTS xenial |
Fixed 38.0.2125.111-0ubuntu1.1103
|
|
14.04 LTS trusty |
Fixed 38.0.2125.111-0ubuntu0.14.04.1.1061
|
|
libv8 | ||
18.04 LTS bionic | Not in release | |
16.04 LTS xenial | Not in release | |
14.04 LTS trusty | Not in release | |
libv8-3.14 | ||
18.04 LTS bionic | Ignored libv8 not supported | |
16.04 LTS xenial | Ignored libv8 not supported | |
14.04 LTS trusty | Not in release | |
oxide-qt | ||
18.04 LTS bionic | Not in release | |
16.04 LTS xenial |
Fixed 1.2.5-0ubuntu1
|
|
14.04 LTS trusty |
Fixed 1.2.5-0ubuntu0.14.04.1
|
|
Notes
References
Related Ubuntu Security Notices (USN)
- USN-2345-1
- Oxide vulnerabilities
- 14 October 2014