# CVE-2014-3195: Information disclosure in n/a

> Remote attackers can obtain sensitive information via crafted JavaScript code exploiting improper memory tracking in the V8 engine.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qj6g-vf38-w7w7, UBUNTU-CVE-2014-3195

## What is CVE-2014-3195?

CVE-2014-3195 is a medium-severity vulnerability in Google Chrome, published on 8 Oct 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-399

## Which versions are affected by CVE-2014-3195?

It affects 5 products.


Products: Google Chrome, Redhat Enterprise Linux Desktop Supplementary, Redhat Enterprise Linux Server Supplementary, Redhat Enterprise Linux Server Supplementary Eus, Redhat Enterprise Linux Workstation Supplementary.

## How do I fix CVE-2014-3195?

Upgrade to a fixed version.

## Is CVE-2014-3195 being exploited?

There is no known exploitation of CVE-2014-3195 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3195 and fix it if it is affected.

What it is: CVE-2014-3195 is a medium-severity vulnerability in Google Chrome, published on 8 Oct 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-3195 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-3195/ (Markdown: https://insights.sbomify.com/CVE-2014-3195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-3195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-3195
- OSV: https://osv.dev/vulnerability/CVE-2014-3195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-3195/
Summaries are generated and may contain mistakes; the official description above is the record.