CVE-2017-16803

Name: CVE-2017-16803
Creator: NVD / NIST
Published: 2017-11-13T17:29:00.567+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.01%

Last modified Jun 17, 2026

CVE-2017-16803 is a vulnerability of currently unknown severity. In Libav through 11.11 and 12.x through 12.1, the smacker_decode_tree function in libavcodec/smacker.c does not properly restrict tree recursion, which allows remote attackers to cause a denial of service (bitstream.c:build_table() out-of-bounds read and application crash) via a crafted Smacker stream.. EPSS estimates a 3.01% chance of exploitation in the next 30 days.

Description

In Libav through 11.11 and 12.x through 12.1, the smacker_decode_tree function in libavcodec/smacker.c does not properly restrict tree recursion, which allows remote attackers to cause a denial of service (bitstream.c:build_table() out-of-bounds read and application crash) via a crafted Smacker stream.

Metrics

EPSS Probability

3.01%

85.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-119

Affected Software

Vendor	Product	Versions
Libav	Libav	<= 11.11
Libav	Libav	12.0
Libav	Libav	12.1

References

http://www.securityfocus.com/bid/101882Third Party Advisory, VDB Entry
https://bugzilla.libav.org/show_bug.cgi?id=1098Issue Tracking
https://github.com/libav/libav/commit/cd4663dc80323ba64989d0c103d51ad3ee0e9c2fIssue Tracking
https://security.gentoo.org/glsa/201811-19
https://www.debian.org/security/2018/dsa-4119
http://www.securityfocus.com/bid/101882Third Party Advisory, VDB Entry
https://bugzilla.libav.org/show_bug.cgi?id=1098Issue Tracking
https://github.com/libav/libav/commit/cd4663dc80323ba64989d0c103d51ad3ee0e9c2fIssue Tracking
https://security.gentoo.org/glsa/201811-19
https://www.debian.org/security/2018/dsa-4119

Timeline

Published: Nov 13, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-16803?

How severe is CVE-2017-16803?

Severity scoring for CVE-2017-16803 is pending analysis. The EPSS model estimates a 3.01% probability of exploitation in the next 30 days.

How do I fix CVE-2017-16803?

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.

Are you affected by CVE-2017-16803?

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

Scan your code now

Source: NVD / NIST