Libproxy

Every one of the 5 is a mark on the map. Named now: 1 to 5, most at risk first.

1. url::recvline in url.cpp in libproxy 0.4.x through 0.4.15 allows a remote HTTP server to trigger uncontrolled recursion via a response composed of an infinite stream that lacks a…CVE-2020-25219Libproxy Project · 4.4% likely

   CWE-674

2. 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.CVE-2020-26154Libproxy Project · 3.6% likely

   CWE-120

3. Stack-based buffer overflow in the url::get_pac function in url.cpp in libproxy 0.4.x before 0.4.9 allows remote servers to have an unspecified impact via a large proxy.pac file.CVE-2012-4504Libproxy Project · 3.5% likely

   CWE-119

4. Heap-based buffer overflow in the px_pac_reload function in lib/pac.c in libproxy 0.2.x and 0.3.x allows remote servers to have an unspecified impact via a crafted Content-Length…CVE-2012-4505Libproxy Project · 3.2% likely

   CWE-119

5. Format string vulnerability in the print_proxies function in bin/proxy.c in libproxy 0.3.1 might allow context-dependent attackers to cause a denial of service (crash) and possibl…CVE-2012-5580Libproxy Project · 3.1% likely

   CWE-94

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.