Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#75360 - [security] [libtiff] CVE-2022-2056 / CVE-2022-2057 / CVE-2022-2058
Attached to Project:
Arch Linux
Opened by T.J. Townsend (blakkheim) - Sunday, 17 July 2022, 22:29 GMT
Last edited by David Runge (dvzrv) - Monday, 01 August 2022, 08:39 GMT
Opened by T.J. Townsend (blakkheim) - Sunday, 17 July 2022, 22:29 GMT
Last edited by David Runge (dvzrv) - Monday, 01 August 2022, 08:39 GMT
|
DetailsDescription:
The libtiff package is vulnerable to CVE-2022-2056, CVE-2022-2057, and CVE-2022-2058. The attached diff applies an upstream commit to fix them. |
This task depends upon
Closed by David Runge (dvzrv)
Monday, 01 August 2022, 08:39 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with libtiff 4.4.0-2 / lib32-libtiff 4.4.0-2
Monday, 01 August 2022, 08:39 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with libtiff 4.4.0-2 / lib32-libtiff 4.4.0-2
tiff.diff
Upstream fixes are applied in 4.4.0-2 in [testing] and [community-testing]. Feedback is much appreciated! :)
Could you possibly add the symbol versioning support as well (https://bugs.archlinux.org/task/71330?project=1&string=libtiff)?
Thanks