CVE-2015-1030
First published: Tue Jan 20 2015(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Privoxy | <=3.0.21 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
How do I fix CVE-2015-1030?
To fix CVE-2015-1030, upgrade Privoxy to version 3.0.22 or later.
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.
Who is affected by CVE-2015-1030?
CVE-2015-1030 affects users running Privoxy versions prior to 3.0.22.
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.
- agent/type
- agent/softwarecombine
- agent/author
- agent/severity
- agent/remedy
- agent/references
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/privoxy
- canonical/privoxy
- version/privoxy/3.0.21