Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1618573 - (CVE-2018-11771) CVE-2018-11771 apache-commons-compress: ZipArchiveInputStream.read() fails to identify correct EOF allowing for DoS via crafted zip
CVE-2018-11771 apache-commons-compress: ZipArchiveInputStream.read() fails to...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180817,repor...
: Security
Depends On: 1618575 1618574 1625463 1625464 1640713 1640717 1640719
Blocks: 1618576
  Show dependency treegraph
 
Reported: 2018-08-16 22:22 EDT by Sam Fowler
Modified: 2018-10-18 11:08 EDT (History)
88 users (show)

See Also:
Fixed In Version: apache-commons-compress 1.18
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-08-16 22:22:45 EDT
Apache Commons Compress versions 1.7 to 1.17 are vulnerable to a denial of service attack via crafted ZIP archive. When reading a specially crafted ZIP archive, the read method of ZipArchiveInputStream can fail to return the correct EOF indication after the end of the stream has been reached.  When combined with a java.io.InputStreamReader this can lead to an infinite stream, which can be used to mount a denial of service attack against services that use Compress' zip package.


External Reference:

https://lists.apache.org/thread.html/b8da751fc0ca949534cdf2744111da6bb0349d2798fac94b0a50f330@%3Cannounce.apache.org%3E
Comment 1 Sam Fowler 2018-08-16 22:23:02 EDT
Created apache-commons-compress tracking bugs for this issue:

Affects: fedora-all [bug 1618574]

Note You need to log in before you can comment on or make changes to this bug.