# CVE-2017-5047: Integer overflow in Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android

> A remote attacker can execute arbitrary code via a crafted video file due to an integer overflow in FFmpeg within Google Chrome.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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:** Yes
- **Published:** 25 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-763w-wjxp-rrxx, UBUNTU-CVE-2017-5047

## What is CVE-2017-5047?

CVE-2017-5047 is a high-severity vulnerability in Google Chrome, published on 25 Apr 2017. 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

An integer overflow in FFmpeg in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android allowed a remote attacker to perform an out of bounds memory write via a crafted video file, related to ChunkDemuxer.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Google Chrome.

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

Upgrade to a fixed version.

## Is CVE-2017-5047 being exploited?

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

What it is: CVE-2017-5047 is a high-severity vulnerability in Google Chrome, published on 25 Apr 2017. 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-5047 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-5047/ (Markdown: https://insights.sbomify.com/CVE-2017-5047/index.md)
```

## Sources

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

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