| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Privoxy 3.0.21. It has been classified as problematic. This issue affects some unknown processing of the component Socket Handler. The manipulation leads to resource management. This vulnerability is listed as CVE-2015-1030. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in Privoxy 3.0.21. It has been rated as problematic. This issue affects an unknown code block of the component Socket Handler. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. The summary by CVE is:
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.
The weakness was presented 01/07/2015 as confirmed mailinglist post (oss-sec). The advisory is shared at seclists.org. The identification of this vulnerability is CVE-2015-1030 since 01/10/2015. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 81086 (Privoxy < 3.0.22 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Firewalls.
Upgrading to version 3.0.22 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (99972), Tenable (81086), SecurityFocus (BID 71991†), Secunia (SA62123†) and Vulnerability Center (SBV-48537†). See VDB-68634, VDB-68979 and VDB-80713 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 81086
Nessus Name: Privoxy < 3.0.22 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Privoxy 3.0.22
Timeline
01/07/2015 🔍01/07/2015 🔍
01/07/2015 🔍
01/07/2015 🔍
01/10/2015 🔍
01/19/2015 🔍
01/20/2015 🔍
01/29/2015 🔍
02/10/2015 🔍
03/02/2022 🔍
Sources
Advisory: seclists.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2015-1030 (🔍)
GCVE (CVE): GCVE-0-2015-1030
GCVE (VulDB): GCVE-100-68633
X-Force: 99972 - Privoxy socket limit denial of service, Medium Risk
SecurityFocus: 71991 - Privoxy CVE-2015-1030 Memory Leak Information Disclosure Vulnerability
Secunia: 62123 - Privoxy Multiple Vulnerabilities, Moderately Critical
Vulnerability Center: 48537 - Privoxy Before 3.0.22 Remote DoS due to Memory Leak in jbsocket.c, Medium
See also: 🔍
Entry
Created: 01/19/2015 09:13Updated: 03/02/2022 15:41
Changes: 01/19/2015 09:13 (68), 06/19/2017 08:43 (5), 03/02/2022 15:41 (3)
Complete: 🔍
Cache ID: 216:CCC:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.