First published: Mon Feb 15 2021(Updated: )
Memory leaks when a response is buffered and the buffer limit is reached or Privoxy is running out of memory Upstream Patch: <a href="https://www.privoxy.org/gitweb/?p=privoxy.git;a=commit;h=bbd53f1010b">https://www.privoxy.org/gitweb/?p=privoxy.git;a=commit;h=bbd53f1010b</a> <a href="https://www.privoxy.org/gitweb/?p=privoxy.git;a=commit;h=4490d451f9b">https://www.privoxy.org/gitweb/?p=privoxy.git;a=commit;h=4490d451f9b</a> External References: <a href="https://www.privoxy.org/3.0.29/user-manual/whatsnew.html">https://www.privoxy.org/3.0.29/user-manual/whatsnew.html</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/Privoxy | <3.0.29 | 3.0.29 |
Privoxy Privoxy | <3.0.29 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-35502 is a vulnerability found in Privoxy versions before 3.0.29 that can lead to a system crash due to memory leaks.
CVE-2020-35502 has a severity score of 7.5, which is considered high.
Privoxy versions before 3.0.29 are affected by CVE-2020-35502.
To fix CVE-2020-35502, update your Privoxy installation to version 3.0.29.
More information about CVE-2020-35502 can be found at the following references: [Bugzilla Red Hat](https://bugzilla.redhat.com/show_bug.cgi?id=1928749), [Gentoo Security](https://security.gentoo.org/glsa/202107-16), [Privoxy User Manual](https://www.privoxy.org/3.0.29/user-manual/whatsnew.html).