Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1300966 (CVE-2016-1982)

Summary:	CVE-2016-1982 privoxy: invalid reads in case of corrupt chunk-encoded content
Product:	[Other] Security Response	Reporter:	Andrej Nemec <anemec>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	gwync, karsten
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	privoxy 3.0.24	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-23 21:07:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1300967, 1300968, 1300969
Bug Blocks:

Description Andrej Nemec 2016-01-22 08:57:19 UTC

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 08:57:53 UTC

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 21:07:05 UTC

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.