CVE-2014-1721
Publication date 9 April 2014
Last updated 24 July 2024
Ubuntu priority
Google V8, as used in Google Chrome before 34.0.1847.116, does not properly implement lazy deoptimization, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code, as demonstrated by improper handling of a heap allocation of a number outside the Small Integer (aka smi) range.
Status
Package | Ubuntu Release | Status |
---|---|---|
chromium-browser | ||
18.04 LTS bionic |
Not affected
|
|
16.04 LTS xenial |
Not affected
|
|
14.04 LTS trusty | Not in release | |
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 |
Not affected
|
|
14.04 LTS trusty | Not in release | |
qtjsbackend-opensource-src | ||
18.04 LTS bionic | Not in release | |
16.04 LTS xenial | Not in release | |
14.04 LTS trusty | Not in release | |
Notes
chrisccoulson
Issue was fixed prior to Oxide r501, the first version to be included in an Ubuntu release
mikesalvatore
The Ubuntu Security Team does not support libv8