# CVE-2017-15402: Other in Chrome

> A compromised renderer can overwrite page state of other frames, enabling sandbox escape via crafted HTML in Chrome on Chrome OS.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** No
- **Published:** 9 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5fmj-pwmm-hx82

## What is CVE-2017-15402?

CVE-2017-15402 is a critical vulnerability in Google Chrome, published on 9 Jan 2019. 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

Using an ID that can be controlled by a compromised renderer which allows any frame to overwrite the page_state of any other frame in the same process in Navigation in Google Chrome on Chrome OS prior to 62.0.3202.74 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-15402?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2017-15402?

No fix has been published for CVE-2017-15402 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-15402 being exploited?

There is no known exploitation of CVE-2017-15402 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-2017-15402 and fix it if it is affected.

What it is: CVE-2017-15402 is a critical vulnerability in Google Chrome, published on 9 Jan 2019. 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-2017-15402 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-2017-15402/ (Markdown: https://insights.sbomify.com/CVE-2017-15402/index.md)
```

## Sources

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

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