CVE-2015-1030: Medium severity privoxy vulnerability
Published Jan 20, 2015
·Updated
Memory leak in the rfc2553connectto function in jbsocket.c in Privoxy before 3.0.22 allows remote attackers to cause a denial of service (memory consumption) via a large number of requests that are rejected because the socket limit is reached.
Affected Software
1 affected component
Privoxy privoxy<=3.0.21
Remediation
Patch Available
Event History
Jan 20, 2015
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2015-1030?
CVE-2015-1030 has a medium severity rating due to its potential to cause a denial of service through memory consumption.
2
How do I fix CVE-2015-1030?
To fix CVE-2015-1030, upgrade Privoxy to version 3.0.22 or later.
3
What causes the vulnerability CVE-2015-1030?
CVE-2015-1030 is caused by a memory leak when the rfc2553_connect_to function processes a large number of rejected requests.
4
Who is affected by CVE-2015-1030?
CVE-2015-1030 affects users running Privoxy versions prior to 3.0.22.
5
What can attackers do with CVE-2015-1030?
Attackers can exploit CVE-2015-1030 to deplete server memory resources, leading to a denial of service.