Your message dated Sat, 28 Jan 2023 15:29:54 +0100
with message-id <bc5f9c67e74a34be7aef3a33bcb9e2bbdb9efcbe.ca...@sviech.de>
and subject line Re: libde265: CVE-2020-21594 CVE-2020-21595 CVE-2020-21596
CVE-2020-21597 CVE-2020-21599 CVE-2020-21601 CVE-2020-21603 CVE-2020-21604
CVE-2020-21605 CVE-2020-21606
has caused the Debian Bug report #1004963,
regarding CVE-2020-21598 CVE-2020-21600 CVE-2020-21602
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1004963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libde265
Version: 1.0.8-1
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team <t...@security.debian.org>
CVE-2020-21602:
https://github.com/strukturag/libde265/issues/242
CVE-2020-21600:
https://github.com/strukturag/libde265/issues/243
CVE-2020-21598:
https://github.com/strukturag/libde265/issues/237
--- End Message ---
--- Begin Message ---
This is fixed already in unstable, so I guess these bugs can be closed.
--- End Message ---
