CVE-2017-5025 Memory corruption in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac

What is CVE-2017-5025?

CVE-2017-5025 is a medium-severity memory corruption vulnerability in Google Chrome, published on 17 Feb 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted video file.

Weakness: CWE-119

Which versions are affected by CVE-2017-5025?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2017-5025?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-5025 being exploited?

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

Other vulnerabilities in Google Chrome

• CVE-2022-4135 Google Chromium GPU Heap Buffer Overflow Exploited Critical 9.6
• CVE-2020-16017 Google Chrome Use-After-Free Exploited Critical 9.6
• CVE-2020-16010 Google Chrome for Android UI Heap Buffer Overflow Exploited Critical 9.6
• CVE-2026-87491 Google Chromium V8 Out of Bounds Write Exploited High 8.8
• CVE-2026-85046 Google Chromium V8 Type Confusion Exploited High 8.8

All Google Chrome vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as ALPINE-CVE-2017-5025, DEBIAN-CVE-2017-5025, GHSA-wm5j-7vrw-x2hq, UBUNTU-CVE-2017-5025.