.. |
CVE-2022-2057.nopatch
|
Fix libtiff CVEs: 2022-2056, 2022-2057, 2022-2058 (#3388)
|
2022-07-15 15:54:48 -07:00 |
CVE-2022-2058.nopatch
|
Fix libtiff CVEs: 2022-2056, 2022-2057, 2022-2058 (#3388)
|
2022-07-15 15:54:48 -07:00 |
CVE-2022-3598.nopatch
|
Patch libtiff for CVE-2022-3597, CVE-2022-3626, CVE-2022-3627, CVE-2022-3599, CVE-2022-3970 (#4204)
|
2022-11-18 12:10:44 -06:00 |
CVE-2022-3626.nopatch
|
Patch libtiff for CVE-2022-3597, CVE-2022-3626, CVE-2022-3627, CVE-2022-3599, CVE-2022-3970 (#4204)
|
2022-11-18 12:10:44 -06:00 |
CVE-2022-3627.nopatch
|
Patch libtiff for CVE-2022-3597, CVE-2022-3626, CVE-2022-3627, CVE-2022-3599, CVE-2022-3970 (#4204)
|
2022-11-18 12:10:44 -06:00 |
CVE-2023-0796.nopatch
|
Patch libtiff for CVE-2023-0795(to 0799) and CVE-2023-0800(to 0804) (#4903)
|
2023-02-28 15:39:02 +05:30 |
CVE-2023-0797.nopatch
|
Patch libtiff for CVE-2023-0795(to 0799) and CVE-2023-0800(to 0804) (#4903)
|
2023-02-28 15:39:02 +05:30 |
CVE-2023-0798.nopatch
|
Patch libtiff for CVE-2023-0795(to 0799) and CVE-2023-0800(to 0804) (#4903)
|
2023-02-28 15:39:02 +05:30 |
CVE-2023-0799.nopatch
|
Patch libtiff for CVE-2023-0795(to 0799) and CVE-2023-0800(to 0804) (#4903)
|
2023-02-28 15:39:02 +05:30 |
CVE-2023-0800.nopatch
|
libtiff: add patch for CVE-2023-0801 (#5517)
|
2023-05-17 01:34:42 -07:00 |
CVE-2023-0802.nopatch
|
libtiff: add patch for CVE-2023-0801 (#5517)
|
2023-05-17 01:34:42 -07:00 |
CVE-2023-0803.nopatch
|
libtiff: add patch for CVE-2023-0801 (#5517)
|
2023-05-17 01:34:42 -07:00 |
CVE-2023-0804.nopatch
|
libtiff: add patch for CVE-2023-0801 (#5517)
|
2023-05-17 01:34:42 -07:00 |
libtiff.signatures.json
|
Update libtiff to v4.6.0 to fix CVE 2023-40745 and 2023-41175 (#6567)
|
2023-10-27 11:05:11 -07:00 |
libtiff.spec
|
Update libtiff to v4.6.0 to fix CVE 2023-40745 and 2023-41175 (#6567)
|
2023-10-27 11:05:11 -07:00 |