Privoxy prior 3.0.33 get_url_spec_param memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in Privoxy. This impacts the function get_url_spec_param. Such manipulation leads to memory leak. This vulnerability is traded as CVE-2021-44540. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Privoxy. It has been rated as problematic. Affected by this issue is the function get_url_spec_param. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability.

The weakness was shared 12/24/2021. The advisory is shared for download at privoxy.org. This vulnerability is handled as CVE-2021-44540 since 12/03/2021. There are known technical details, but no exploit is available.

Upgrading to version 3.0.33 eliminates this vulnerability. The upgrade is hosted for download at privoxy.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at privoxy.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Privoxy 3.0.33
Patch: privoxy.org

Timelineinfo

12/03/2021 🔍
12/24/2021 +21 days 🔍
12/24/2021 +0 days 🔍
12/27/2021 +3 days 🔍

Sourcesinfo

Advisory: privoxy.org
Status: Confirmed

CVE: CVE-2021-44540 (🔍)
GCVE (CVE): GCVE-0-2021-44540
GCVE (VulDB): GCVE-100-189044

Entryinfo

Created: 12/24/2021 08:20
Updated: 12/27/2021 08:33
Changes: 12/24/2021 08:20 (39), 12/27/2021 08:33 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!