Information Disclosure

Every one of the 6 is a mark on the map. Named now: 1 to 6, most at risk first.

1. FFmpeg before 2.8.12, 3.0.x and 3.1.x before 3.1.9, 3.2.x before 3.2.6, and 3.3.x before 3.3.2 does not properly restrict HTTP Live Streaming filename extensions and demuxer names…CVE-2017-9993Ffmpeg · 16% likely

   CWE-200

2. FFmpeg 2.x allows remote attackers to conduct cross-origin attacks and read arbitrary files by using the concat protocol in an HTTP Live Streaming (HLS) M3U8 file, leading to an e…CVE-2016-1897Ffmpeg · 15% likely

   CWE-200

3. FFmpeg 2.x allows remote attackers to conduct cross-origin attacks and read arbitrary files by using the subfile protocol in an HTTP Live Streaming (HLS) M3U8 file, leading to an…CVE-2016-1898Ffmpeg · 13% likely

   CWE-200

4. The avi_read_header function in libavformat/avidec.c in FFmpeg before 3.1.4 is vulnerable to memory leak when decoding an AVI file that has a crafted "strh" structure.CVE-2016-7555Ffmpeg · 1.4% likely

   CWE-200

5. Prior to ffmpeg version 4.3, the tty demuxer did not have a 'read_probe' function assigned to it. By crafting a legitimate "ffconcat" file that references an image, followed by a…CVE-2021-3566Ffmpeg · 0.9% likely

   CWE-200

6. FFmpeg git-master before commit d5873b was discovered to contain a memory leak in the component libavutil/mem.c.CVE-2025-25468Ffmpeg · CVSS 6.5 · 0.4% likely

   CWE-200

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.