CVE-2021-44541
First published: Thu Dec 23 2021(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Privoxy Privoxy | <3.0.33 |
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-2021-44541?
The severity of CVE-2021-44541 is high with a severity value of 7.5.
How does CVE-2021-44541 affect Privoxy?
CVE-2021-44541 affects Privoxy versions up to and excluding 3.0.33.
What is the impact of CVE-2021-44541?
CVE-2021-44541 could allow attackers to cause a denial of service or possibly execute arbitrary code.
How was CVE-2021-44541 fixed?
CVE-2021-44541 was fixed in Privoxy by freeing header memory when failing to get the request destination.
Where can I find more information about CVE-2021-44541?
More information about CVE-2021-44541 can be found at the following references: [1](https://www.privoxy.org/3.0.33/user-manual/whatsnew.html) and [2](https://www.privoxy.org/gitweb/?p=privoxy.git;a=commit;h=652b4b7cb0).
- agent/references
- agent/type
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/author
- agent/severity
- agent/remedy
- agent/tags
- agent/weakness
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- vendor/privoxy
- canonical/privoxy privoxy