Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2014-3195

Google V8, as used in Google Chrome before 38.0.2125.101, does not properly track JavaScript heap-memory allocations as allocations of…

Medium5.0EPSS 1.3%
Published
Updated
Reserved
Assigned by
Chrome

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.

Scores

CVSS scores of CVE-2014-3195, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified2.0Medium5.0AV:N/AC:L/Au:N/C:P/I:N/A:N
EPSS (exploitation in 30 days)
1.3% · top 30% of all CVEs (4 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.0.

Weakness

Affected products

  • n/a

    • affected n/a

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2014-3195 badge
[![CVE-2014-3195](https://trackcve.app/badge/CVE-2014-3195.svg)](https://trackcve.app/cve/CVE-2014-3195)

Record last updated .