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 1169213 - (CVE-2015-1030) CVE-2015-1030 privoxy: potential flaws fixed in version 3.0.22
CVE-2015-1030 privoxy: potential flaws fixed in version 3.0.22
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=20141128,repor...
: Security
Depends On:
Blocks: 1169216
  Show dependency treegraph
 
Reported: 2014-11-30 23:30 EST by Murray McAllister
Modified: 2015-03-20 03:47 EDT (History)
6 users (show)

See Also:
Fixed In Version: privoxy 3.0.22
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-19 06:14:58 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 Murray McAllister 2014-11-30 23:30:08 EST
The 3.0.22 release of Privoxy fixes the following potential flaws:

""
Fixed a memory leak when rejecting client connections due to
the socket limit being reached (CID 66382). This affected
Privoxy 3.0.21 when compiled with IPv6 support (on most
platforms this is the default).

Fixed an immediate-use-after-free bug (CID 66394) and two
additional unconfirmed use-after-free complaints made by
Coverity scan (CID 66391, CID 66376).
""

Version 3.0.22 is already in the Fedora and EPEL 6 testing repositories.

Reference:

http://www.privoxy.org/announce.txt
Comment 3 Martin Prpič 2015-01-12 07:19:18 EST
(In reply to Murray McAllister from comment #0)
> Fixed a memory leak when rejecting client connections due to
> the socket limit being reached (CID 66382). This affected
> Privoxy 3.0.21 when compiled with IPv6 support (on most
> platforms this is the default).

This was assigned CVE-2015-1030.

> 
> Fixed an immediate-use-after-free bug (CID 66394) and two
> additional unconfirmed use-after-free complaints made by
> Coverity scan (CID 66391, CID 66376).

This was assigned CVE-2015-1031.

http://seclists.org/oss-sec/2015/q1/111
Comment 4 Vasyl Kaigorodov 2015-01-21 06:51:04 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2015-1201 to
the following vulnerability:

Name: CVE-2015-1201
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1201
Assigned: 20150120
Reference: http://secunia.com/advisories/62123

Privoxy before 3.0.22 allows remote attackers to cause a denial of
service (file descriptor consumption) via unspecified vectors.  NOTE:
the provenance of this information is unknown; the details are
obtained solely from third party information.
Comment 5 Siddharth Sharma 2015-02-25 05:03:50 EST
upstream fixes
==============

CVE-2015-1030
-------------

Fixed a memory leak when rejecting client connections due to
the socket limit being reached (CID 66382). This affected
Privoxy 3.0.21 when compiled with IPv6 support (on most
platforms this is the default).

Links:
http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/cgisimple.c?view=log

http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/cgisimple.c?view=log&pathrev=v_3_0_22

Patch: http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/cgisimple.c?view=patch&r1=1.130&r2=1.131&pathrev=v_3_0_22


CVE-2015-1031
-------------

Fixed an immediate-use-after-free bug (CID 66394) and two
additional unconfirmed use-after-free complaints made by
Coverity scan (CID 66391, CID 66376).

Links:

http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/list.c?view=log&pathrev=v_3_0_22

Patch: http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/list.c?view=patch&r1=1.31&r2=1.32&pathrev=v_3_0_22
Comment 6 Vasyl Kaigorodov 2015-03-18 08:57:27 EDT
CVE-2015-1201 has been split to https://bugzilla.redhat.com/1203237
CVE-2015-1031 has been split to https://bugzilla.redhat.com/1203242

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