Описание
url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header.
url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2020-26154
- https://github.com/libproxy/libproxy/pull/126
- https://bugs.debian.org/968366
- https://lists.debian.org/debian-lts-announce/2020/11/msg00024.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3BID3HVHAF6DA3YJOFDBSAZSMR3ODNIW
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WZVZXTFMFTSML3J6OOCDBDYH474BRJSW
- https://www.debian.org/security/2020/dsa-4800
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00030.html
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00033.html
Связанные уязвимости
url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header.
url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header.
url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header.
url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when ...