Linux · Ubuntu · Package update · March 5, 2018

libzzip-0-13 0.13.62-3.1ubuntu0.18.04.1: libzzip-0-13 0.13.62-3.1ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)

libzzip-0-13 0.13.62-3.1ubuntu0.18.04.1, released March 5, 2018, fixes 7 CVEs in libzzip-0-13. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

RoutineUnsupported product
CVEs closed
7
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0280
86th percentile

Priority of the 7 CVEs

Patch now 0 Urgent 0 High 0 Routine 7

Fixed package versions

ProductReleaseFixed in
libzzip-0-13Ubuntu 18.04.6 LTS (bionic)0.13.62-3.1ubuntu0.18.04.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Routine CVE-2018-6869 libzzip-0-13: In ZZIPlib 0.13.68, there is an uncontrolled memory allocation and a crash in the __zzip_parse_root_directory functio...n/a 0.0280 None reported
Routine CVE-2018-6540 libzzip-0-13: In ZZIPlib 0.13.67, there is a bus error caused by loading of a misaligned address in the zzip_disk_findfirst functio...n/a 0.0226 None reported
Routine CVE-2018-6541 libzzip-0-13: In ZZIPlib 0.13.67, there is a bus error caused by loading of a misaligned address (when handling disk64_trailer loca...n/a 0.0226 None reported
Routine CVE-2018-6484 libzzip-0-13: In ZZIPlib 0.13.67, there is a memory alignment error and bus error in the __zzip_fetch_disk_trailer function of zzip...n/a 0.0224 None reported
Routine CVE-2018-6381 libzzip-0-13: In ZZIPlib 0.13.67, 0.13.66, 0.13.65, 0.13.64, 0.13.63, 0.13.62, 0.13.61, 0.13.60, 0.13.59, 0.13.58, 0.13.57 and 0.13...n/a 0.0170 None reported
Routine CVE-2018-7725 libzzip-0-13: An issue was discovered in ZZIPlib 0.13.68n/a 0.0169 None reported
Routine CVE-2018-7726 libzzip-0-13: An issue was discovered in ZZIPlib 0.13.68n/a 0.0169 None reported
Showing 1 to 7 of 7 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.