CVE-2022-2566: Heap-memory write in FFMPEG

Published Sep 23, 2022

Updated

A heap out-of-bounds memory write exists in FFMPEG since version 5.1. The size calculation in buildopengopkeypoints() goes through all entries in the loop and adds sc->cttsdata[i].count to sc->sampleoffsetscount. This can lead to an integer overflow resulting in a small allocation with avcalloc(). An attacker can cause remote code execution via a malicious mp4 file. We recommend upgrading past commit c953baa084607dd1d84c3bfcce3cf6a87c3e6e05

Affected Software

1 affected component

FFmpeg FFmpeg=5.1

Remediation

Patch Available

https://github.com/FFmpeg/FFmpeg/commit/c953baa084607dd1d84c3bfcce3cf6a87c3e6e05

Event History

Sep 23, 2022

CVE Published

via MITRE·11:10 AM

Data Sourced

via MITRE·11:10 AM

DescriptionSeverityWeakness

Frequently Asked Questions

What is the vulnerability ID for this FFMPEG vulnerability?

The vulnerability ID for this FFMPEG vulnerability is CVE-2022-2566.

What is the severity of CVE-2022-2566?

The severity of CVE-2022-2566 is critical with a CVSS score of 7.8.

Which version of FFMPEG is affected by CVE-2022-2566?

FFMPEG version 5.1 is affected by CVE-2022-2566.

What is the impact of CVE-2022-2566?

CVE-2022-2566 can lead to an integer overflow resulting in a small allocation with potential for code execution, denial of service, or information disclosure.

Is there a fix available for CVE-2022-2566?

Yes, a fix is available for CVE-2022-2566. It is recommended to update to a fixed version of FFMPEG.