Strix
26.1K

CVE-2006-4800

UnknownEPSS 4.90%

Last modified

CVE-2006-4800 is a vulnerability of currently unknown severity. Multiple buffer overflows in libavcodec in ffmpeg before 0.4.9_p20060530 allow remote attackers to cause a denial of service or possibly execute arbitrary code via multiple unspecified vectors in (1) dtsdec.c, (2) vorbis.c, (3) rm.c, (4) sierravmd.c, (5) smacker.c, (6) tta.c, (7) 4xm.c, (8) alac.c, (9) cook.c, (10) shorten.c, (11) smacker.c, (12) snow.c, and (13) tta.c. NOTE: it is likely that this is a different vulnerability than CVE-2005-4048 and CVE-2006-2802.. EPSS estimates a 4.90% chance of exploitation in the next 30 days.

Description

Multiple buffer overflows in libavcodec in ffmpeg before 0.4.9_p20060530 allow remote attackers to cause a denial of service or possibly execute arbitrary code via multiple unspecified vectors in (1) dtsdec.c, (2) vorbis.c, (3) rm.c, (4) sierravmd.c, (5) smacker.c, (6) tta.c, (7) 4xm.c, (8) alac.c, (9) cook.c, (10) shorten.c, (11) smacker.c, (12) snow.c, and (13) tta.c. NOTE: it is likely that this is a different vulnerability than CVE-2005-4048 and CVE-2006-2802.

Metrics

EPSS Probability
4.90%

91.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
FfmpegFfmpeg0.4.6
FfmpegFfmpeg0.4.7
FfmpegFfmpeg0.4.8
FfmpegFfmpeg0.4.9

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2006-4800?
Multiple buffer overflows in libavcodec in ffmpeg before 0.4.9_p20060530 allow remote attackers to cause a denial of service or possibly execute arbitrary code via multiple unspecified vectors in (1) dtsdec.c, (2) vorbis.c, (3) rm.c, (4) sierravmd.c, (5) smacker.c, (6) tta.c, (7) 4xm.c, (8) alac.c, (9) cook.c, (10) shorten.c, (11) smacker.c, (12) snow.c, and (13) tta.c. NOTE: it is likely that this is a different vulnerability than CVE-2005-4048 and CVE-2006-2802.
How severe is CVE-2006-4800?
Severity scoring for CVE-2006-4800 is pending analysis. The EPSS model estimates a 4.90% probability of exploitation in the next 30 days.
How do I fix CVE-2006-4800?
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

Related CVEs from 2006

View all 2006CVEs →

Are you affected by CVE-2006-4800?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST