CVE-2013-7016: Buffer Overflow

Published Dec 9, 2013
·
Updated

The getsiz function in libavcodec/jpeg2000dec.c in FFmpeg before 2.1 does not ensure the expected sample separation, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted JPEG2000 data.

Affected Software

64 affected components
FFmpeg FFmpeg<=2.0.1
FFmpeg FFmpeg=0.3
FFmpeg FFmpeg=0.3.1
FFmpeg FFmpeg=0.3.2
FFmpeg FFmpeg=0.3.3
FFmpeg FFmpeg=0.3.4
FFmpeg FFmpeg=0.4.0
FFmpeg FFmpeg=0.4.2
FFmpeg FFmpeg=0.4.3
FFmpeg FFmpeg=0.4.4
FFmpeg FFmpeg=0.4.5
FFmpeg FFmpeg=0.4.6
FFmpeg FFmpeg=0.4.7
FFmpeg FFmpeg=0.4.8
FFmpeg FFmpeg=0.4.9-pre1
FFmpeg FFmpeg=0.5
FFmpeg FFmpeg=0.5.1
FFmpeg FFmpeg=0.5.2
FFmpeg FFmpeg=0.5.3
FFmpeg FFmpeg=0.5.4
FFmpeg FFmpeg=0.5.4.5
FFmpeg FFmpeg=0.5.4.6
FFmpeg FFmpeg=0.5.5
FFmpeg FFmpeg=0.6
FFmpeg FFmpeg=0.6.1
FFmpeg FFmpeg=0.6.2
FFmpeg FFmpeg=0.6.3
FFmpeg FFmpeg=0.7
FFmpeg FFmpeg=0.7.1
FFmpeg FFmpeg=0.7.2
FFmpeg FFmpeg=0.7.3
FFmpeg FFmpeg=0.7.4
FFmpeg FFmpeg=0.7.5
FFmpeg FFmpeg=0.7.6
FFmpeg FFmpeg=0.7.7
FFmpeg FFmpeg=0.7.8
FFmpeg FFmpeg=0.7.9
FFmpeg FFmpeg=0.7.11
FFmpeg FFmpeg=0.7.12
FFmpeg FFmpeg=0.8.0
FFmpeg FFmpeg=0.8.1
FFmpeg FFmpeg=0.8.2
FFmpeg FFmpeg=0.8.5
FFmpeg FFmpeg=0.8.5.3
FFmpeg FFmpeg=0.8.5.4
FFmpeg FFmpeg=0.8.6
FFmpeg FFmpeg=0.8.7
FFmpeg FFmpeg=0.8.8
FFmpeg FFmpeg=0.8.10
FFmpeg FFmpeg=0.8.11
FFmpeg FFmpeg=0.9
FFmpeg FFmpeg=0.9.1
FFmpeg FFmpeg=0.10
FFmpeg FFmpeg=0.10.3
FFmpeg FFmpeg=0.10.4
FFmpeg FFmpeg=0.11
FFmpeg FFmpeg=1.0
FFmpeg FFmpeg=1.1.1
FFmpeg FFmpeg=1.1.2
FFmpeg FFmpeg=1.1.3
FFmpeg FFmpeg=1.1.4
FFmpeg FFmpeg=1.2
FFmpeg FFmpeg=1.2.1
FFmpeg FFmpeg=2.0

Event History

Dec 9, 2013
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description
Data Sourced
via NVD·04:36 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2013-7016?

CVE-2013-7016 has a severity rating that can lead to denial of service due to out-of-bounds array access.

2

How do I fix CVE-2013-7016?

To mitigate CVE-2013-7016, upgrade to FFmpeg version 2.1 or later.

3

What versions of FFmpeg are affected by CVE-2013-7016?

CVE-2013-7016 affects all FFmpeg versions prior to 2.1, including several 0.x and 1.x versions.

4

What type of attack does CVE-2013-7016 facilitate?

CVE-2013-7016 allows remote attackers to exploit crafted JPEG2000 data, potentially leading to application crashes.

5

Is CVE-2013-7016 a widespread vulnerability?

While CVE-2013-7016 affects numerous versions of FFmpeg, the actual impact depends on the specific usage of FFmpeg in applications.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203