The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Gentoo Linux | — | Upgrade www-client/chromium. | Oct 30, 2017 | Oct 8, 2014 |
| Google Chrome | — | Upgrade to the latest version of Google Chrome | Oct 10, 2014 | Oct 7, 2014 |
| Suse | — | Upgrade chromium | Dec 18, 2015 | Oct 8, 2014 |
| Ubuntu | — | Upgrade oxideqt-codecsUpgrade oxideqt-codecs-extraUpgrade liboxideqtcore0 | Nov 8, 2024 | Oct 8, 2014 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub