Privoxy prior 3.0.33 process_encrypted_request_headers memory leak
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Privoxy and classified as problematic. Affected is the function process_encrypted_request_headers. Performing a manipulation results in memory leak.
This vulnerability is known as CVE-2021-44541. No exploit is available.
The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in Privoxy. This affects the function process_encrypted_request_headers. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability.
The weakness was published 12/24/2021. The advisory is shared at privoxy.org. This vulnerability is uniquely identified as CVE-2021-44541 since 12/03/2021. Technical details are known, 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: 🔍
Exploiting
Class: Memory leakCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Privoxy 3.0.33
Patch: privoxy.org
Timeline
12/03/2021 🔍12/24/2021 🔍
12/24/2021 🔍
12/27/2021 🔍
Sources
Advisory: privoxy.orgStatus: Confirmed
CVE: CVE-2021-44541 (🔍)
GCVE (CVE): GCVE-0-2021-44541
GCVE (VulDB): GCVE-100-189045
Entry
Created: 12/24/2021 08:21Updated: 12/27/2021 08:37
Changes: 12/24/2021 08:21 (39), 12/27/2021 08:37 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.