CVE-2017-5024
UnknownEPSS 1.12%
Last modified
CVE-2017-5024 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.12% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 55.0.2883.87 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5024?
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.
How severe is CVE-2017-5024?
Severity scoring for CVE-2017-5024 is pending analysis. The EPSS model estimates a 1.12% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5024?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-5018Google Chrome prior to 56.0.2924.76 for Linux, Windows and M…
- CVE-2017-5019A use after free in Google Chrome prior to 56.0.2924.76 for …
- CVE-2017-5020Google Chrome prior to 56.0.2924.76 for Linux, Windows and M…
- CVE-2017-5021A use after free in Google Chrome prior to 56.0.2924.76 for …
- CVE-2017-5022Blink in Google Chrome prior to 56.0.2924.76 for Linux, Wind…
- CVE-2017-5023Type confusion in Histogram in Google Chrome prior to 56.0.2…
- CVE-2017-5025FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Win…
- CVE-2017-5026Google Chrome prior to 56.0.2924.76 for Linux, Windows and M…
- CVE-2017-5027Blink in Google Chrome prior to 56.0.2924.76 for Linux, Wind…
- CVE-2017-5028Insufficient data validation in V8 in Google Chrome prior to…
- CVE-2017-5029The xsltAddTextString function in transform.c in libxslt 1.1…8.8
- CVE-2017-5030Incorrect handling of complex species in V8 in Google Chrome…8.8
Are you affected by CVE-2017-5024?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST