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 1300966 - (CVE-2016-1982) CVE-2016-1982 privoxy: invalid reads in case of corrupt chunk-encoded content
CVE-2016-1982 privoxy: invalid reads in case of corrupt chunk-encoded content
Status: CLOSED WONTFIX
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=20160121,repor...
: Security
Depends On: 1300967 1300968 1300969
Blocks: 1300970
  Show dependency treegraph
 
Reported: 2016-01-22 03:57 EST by Andrej Nemec
Modified: 2016-05-23 17:07 EDT (History)
2 users (show)

See Also:
Fixed In Version: privoxy 3.0.24
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-23 17:07:05 EDT
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 Andrej Nemec 2016-01-22 03:57:19 EST
A vulnerabily was discovered in a way the privoxy deals with corrupted chunk-encoded content. A maliciously crafted input can result in a remote denial of service.

CVE assignment:

http://seclists.org/oss-sec/2016/q1/179

External reference:

http://seclists.org/oss-sec/2016/q1/173

Upstream fix:

http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/filters.c?r1=1.196&r2=1.197
Comment 1 Andrej Nemec 2016-01-22 03:57:53 EST
Created privoxy tracking bugs for this issue:

Affects: fedora-all [bug 1300967]
Affects: epel-6 [bug 1300968]
Affects: epel-7 [bug 1300969]
Comment 2 Tomas Hoger 2016-05-23 17:07:05 EDT
Buffer over-read issue, possibly leading to crash.  The privoxy is only included in Red Hat Enterprise Linux 5, which is in Phase 3 of its life cycle, and is therefore not planned to have this issue corrected.

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