Unscored severity · published Jan 20, 2015
CVE-2015-1030
Memory leak in the rfc2553_connect_to 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…
–
CVSS
2.4%
EPSS
No
On KEV
Description
Memory leak in the rfc2553_connect_to 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.
Exploitation
Is it being used?
Exploit prediction (EPSS)2.4% · higher than 84% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PR
Privoxy · Privoxy
through 3.0.21 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2015-1030
CVE.org
https://www.cve.org/CVERecord?id=CVE-2015-1030
secunia.com
http://secunia.com/advisories/62123
www.openwall.com
http://www.openwall.com/lists/oss-security/2015/01/11/1
Patch
http://www.privoxy.org/announce.txt
More from Privoxy
7.8
CVE-2019-3699
UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of privoxy on openSUSE Leap 15.1, Factory allows local attackers to escalate from user privoxy to root
7.5
CVE-2021-44542
A memory leak vulnerability was found in Privoxy when handling errors
7.5
CVE-2021-44541
A vulnerability was found in Privoxy which was fixed in process_encrypted_request_headers() by freeing header memory when failing to get the request destination
7.5
CVE-2021-44540
A vulnerability was found in Privoxy which was fixed in get_url_spec_param() by freeing memory of compiled pattern spec before bailing
7.5
CVE-2021-20209
A memory leak vulnerability was found in Privoxy before 3.0.29 in the show-status CGI handler when no action files are configured