FS#53133 - [zziplib] Multiple CVEs
Attached to Project:
Arch Linux
Opened by Santiago Torres (sangy) - Wednesday, 01 March 2017, 20:37 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 18 January 2018, 20:36 GMT
Opened by Santiago Torres (sangy) - Wednesday, 01 March 2017, 20:37 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 18 January 2018, 20:36 GMT
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Thursday, 18 January 2018, 20:36 GMT
Reason for closing: Fixed
Additional comments about closing: Most things are fixed. There will be a followup.
Thursday, 18 January 2018, 20:36 GMT
Reason for closing: Fixed
Additional comments about closing: Most things are fixed. There will be a followup.
history mentions CVE-2017-5974, CVE-2017-5975, CVE-2017-5976, CVE-2017-5978
and CVE-2017-5981[2] - which covers all CVEs with arbitrary code execution.
But I don't know if they're completely fixed by those commits,
that would still need some investigating of the code changes.
[1] https://github.com/gdraheim/zziplib/blob/master/ChangeLog#L14
[2] https://github.com/gdraheim/zziplib/search?q=cve&type=Commits&utf8=%E2%9C%93
CVE-2017-5981
CVE-2017-5974
CVE-2017-5976
CVE-2017-5978
CVE-2017-5975
I can't be completely sure yet, so I'll run the code through the reproducers and let you know.
https://www.suse.com/support/update/announcement/2017/suse-su-20171095-1/
CVE-2017-5981 - Fixed
CVE-2017-5974 - Can't reproduce (It appears this only affected the 32-bit lib)
CVE-2017-5976 - Fixed
CVE-2017-5978 - Fixed
CVE-2017-5975 - Fixed
I'll go on and mark those as resolved. As of now we still have:
CVE-2017-5980
CVE-2017-5979
CVE-2017-5977
I separated these by upstream commit values, the patches were directly obtained from[1]
03de3beabbf570474a9ac05d6dc6b42cdb184cd1 CVE-2017-5974
64e745f8a3604ba1c444febed86b5e142ce03dd7 and 33d6e9c52fcf1a8983896a512033994dc2ca5734 CVE-2017-5975
03de3beabbf570474a9ac05d6dc6b42cdb184cd1 CVE-2017-5976
PATCH NOT FOUND CVE-2017-5977 (this is apparently not fixed, as there is not a patch from opensuse or any mention of it on the changelog)
03de3beabbf570474a9ac05d6dc6b42cdb184cd1 CVE-2017-5978
PATCH NOT IN UPSTREAM CVE-2017-5979 (this is just replacing a malloc to a calloc call...)
PATCH NOT FOUND CVE-2017-5980 (this is apparently not fixed, as there is not a patch from opensuse or any mention of it on the changelog)
3810583f4dee1bac8f02ab41e01bbffd9d6bc286 and 0ce576bdcb330c40cc39636c6232ced0e1bc806b CVE-2017-5981
http://download.opensuse.org/tumbleweed/repo/src-oss/suse/src/zziplib-0.13.62-9.1.src.rpm
CVE-2017-5980
CVE-2017-5978
CVE-2017-5977
CVE-2017-5974:
https://github.com/gdraheim/zziplib/commit/9e8f867a976311a3e5fb0184c947e22ec35f2fcb
https://github.com/gdraheim/zziplib/commit/03de3beabbf570474a9ac05d6dc6b42cdb184cd1
CVE-2017-5975:
https://github.com/gdraheim/zziplib/commit/64e745f8a3604ba1c444febed86b5e142ce03dd7
https://github.com/gdraheim/zziplib/commit/33d6e9c52fcf1a8983896a512033994dc2ca5734
CVE-2017-5976:
https://github.com/gdraheim/zziplib/commit/9e8f867a976311a3e5fb0184c947e22ec35f2fcb
https://github.com/gdraheim/zziplib/commit/03de3beabbf570474a9ac05d6dc6b42cdb184cd1
CVE-2017-5977:
https://github.com/gdraheim/zziplib/commit/9e8f867a976311a3e5fb0184c947e22ec35f2fcb
https://github.com/gdraheim/zziplib/commit/1e5b1ac48186e34e871945769623becfa3650956
The closed github issue:
https://github.com/gdraheim/zziplib/issues/3
CVE-2017-5978:
https://github.com/gdraheim/zziplib/commit/98403bb3c0661e56a2185777fd244ba3a67bc220
CVE-2017-5979:
https://github.com/gdraheim/zziplib/commit/90338371e062eb26d5a5a7bb9c299206d0fef278
CVE-2017-5980:
Open github issue, because not all occurrence are fixed:
https://github.com/gdraheim/zziplib/issues/4
but in debian bug tracker Moritz Muehlenhoff has confirmed with the reproducers that it's fixed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854727#56
and debian mark the CVE as fixed: https://security-tracker.debian.org/tracker/CVE-2017-5980
CVE-2017-5981:
https://github.com/gdraheim/zziplib/commit/0ce576bdcb330c40cc39636c6232ced0e1bc806b
CVE-2017-5980 is still unfixed, denial of service through nullptr dereference. I can create a separate issue if you wish, we gonna issue an advisory for the current version anyway?!
cheers :)