-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 09 Dec 2017 19:39:28 +
Source: linux
Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4
linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha
linux-headers-3.2.0-4-common
Package: thunderbird
Version: 1:52.5.0-1~deb7u1
CVE ID : CVE-2017-7826 CVE-2017-7828 CVE-2017-7830
Multiple security issues have been found in the Mozilla Thunderbird mail
client: Multiple memory safety errors, use after free and other
implementation errors may lead to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 07 Dec 2017 23:45:37 +0100
Source: thunderbird
Binary: thunderbird thunderbird-dev thunderbird-dbg lightning
calendar-google-provider thunderbird-l10n-all thunderbird-l10n-ar
thunderbird-l10n-ast thunderbird-l10n-be
Hi Diego,
I've had a look at CVE-2015-8218 and couldn't reproduce it with the
sample. After further investigations it's pretty clear to me that
libav v0.8.21 and libav v9.21 aren't affected.
Further explanations below.
--
The issue described by CVE-2015-8218 occurs in the decode_uncompressed
Hi,
I have updated my patch for reportbug. Now emails are sent only to one
of the team mailing lists based on the release number in the version
string. There is apparently no simple way to determine the relationship
between release number, code name, suite and whether this is a LTS
release. So we
