Vulnerability Database · Debian · libav · Version

libav 6:0.8.17-2 deb7u1

6:0.8.17-2 deb7u1 is affected by 6 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 0 Medium 0 Low 0 Unrated 6

Database updated 23/Oct/2026

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

libav 6:0.8.17-2 deb7u1 vulnerabilities

6 vulnerabilities cover libav 6:0.8.17-2 deb7u1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Security Update for libav N/A unrated 6:0.8.21-0+deb7u1 21 Oct 2017
Integer Overflow Vulnerability in libav N/A unrated 6:0.8.20-0+deb7u1 19 Jan 2017
Vulnerability in libav - Security Update N/A unrated 6:0.8.19-0+deb7u1 12 Jan 2017
Security Update for libav N/A unrated 6:0.8.18-0+deb7u1 04 Oct 2016
Memory Corruption Vulnerability in libav N/A unrated 6:0.8.17-2+deb7u2 14 Jun 2016
Security Update for libav N/A unrated 6:0.8.17-2 04 Mar 2016

Looking for another version, or everything Vulert holds for libav?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libav 6:0.8.17-2 deb7u1

Is libav 6:0.8.17-2 deb7u1 vulnerable?

Yes. 6 vulnerabilities in the Vulert database cover libav 6:0.8.17-2 deb7u1: 0 critical, 0 high, 0 medium and 0 low, plus 6 not yet rated. Each entry above names the fixed version to move to.

How do I monitor libav for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libav version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.