Bug 1554676 (CVE-2018-7727) - CVE-2018-7727 zziplib: Memory leak in memdisk.c:zzip_mem_disk_new() can lead to denial of service via crafted zip
Summary: CVE-2018-7727 zziplib: Memory leak in memdisk.c:zzip_mem_disk_new() can lead ...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-7727
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1554673 1555082 1558891
Blocks: 1554666
TreeView+ depends on / blocked
 
Reported: 2018-03-13 06:58 UTC by Sam Fowler
Modified: 2019-09-29 14:35 UTC (History)
3 users (show)

Fixed In Version: zziplib 0.13.69
Doc Type: If docs needed, set a value
Doc Text:
A memory leak was found in unzip-mem.c and unzzip-mem.c of ZZIPlib, up to v0.13.68, that could lead to resource exhaustion. Local attackers could leverage this vulnerability to cause a denial of service via a crafted zip file.
Clone Of:
Environment:
Last Closed: 2019-06-10 10:17:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3229 0 None None None 2018-10-30 07:52:15 UTC

Description Sam Fowler 2018-03-13 06:58:11 UTC 
ZZIPlib through version 0.13.68 is vulnerable to a memory leak in
unzzipcat-mem.c:unzzip_cat() and unzip-mem.c:main(), where a ZZIP_MEM_DISK is
allocated but not released. An attacker could exploit this to cause a denial of
service via a crafted zip file.


Upstream Issue:
https://github.com/gdraheim/zziplib/issues/40

Upstream Patches:
https://github.com/gdraheim/zziplib/commit/83a2da55922f67e07f22048ac9671a44cc0d35c4
Comment 1 Sam Fowler 2018-03-13 07:05:32 UTC 
Created zziplib tracking bugs for this issue:

Affects: fedora-all [bug 1554673]
Comment 5 errata-xmlrpc 2018-10-30 07:52:10 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2018:3229 https://access.redhat.com/errata/RHSA-2018:3229
Note You need to log in before you can comment on or make changes to this bug.