CVE-2014-3195
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| chrome | {"endIncluding":"38.0.2125.7"} | |
References
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html
- http://rhn.redhat.com/errata/RHSA-2014-1626.html
- http://www.securityfocus.com/bid/70273
- https://code.google.com/p/v8/source/detail?r=23144
- https://code.google.com/p/v8/source/detail?r=23268
- https://crbug.com/403409
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html
- http://rhn.redhat.com/errata/RHSA-2014-1626.html
- http://www.securityfocus.com/bid/70273
- https://code.google.com/p/v8/source/detail?r=23144
- https://code.google.com/p/v8/source/detail?r=23268
- https://crbug.com/403409
CWEs
CWE-399
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.