Total
7 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2005-1953 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 7.5 HIGH | N/A |
| Heap-based buffer overflow in the CGI extension for Pico Server (pServ) 3.3 allows remote attackers to execute arbitrary code via a long HTTP request. | |||||
| CVE-2005-1952 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 7.5 HIGH | N/A |
| Directory traversal vulnerability in Pico Server (pServ) 3.3 allows remote attackers to read arbitrary files and execute arbitrary commands via a /./ (slash dot slash) before each .. (dot dot) sequence in the URL, which results in an incorrect directory depth count. | |||||
| CVE-2005-1626 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 7.5 HIGH | N/A |
| Multiple buffer overflows in handlers.c for Pico Server (pServ) before 3.3 may allow attackers to execute arbitrary code. | |||||
| CVE-2005-1367 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 7.5 HIGH | N/A |
| Pico Server (pServ) 3.2 and earlier allows local users to read arbitrary files as the pServ user via a symlink to a file outside of the web document root. | |||||
| CVE-2005-1366 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 7.5 HIGH | N/A |
| Pico Server (pServ) 3.2 and earlier allows remote attackers to obtain the source code for CGI scripts via "dirname/../cgi-bin" in a URL. | |||||
| CVE-2005-1365 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 10.0 HIGH | N/A |
| Pico Server (pServ) 3.2 and earlier allows remote attackers to execute arbitrary commands via a URL with multiple leading "/" (slash) characters and ".." sequences. | |||||
| CVE-2002-2295 | 1 Pico Server | 1 Pico Server | 2024-11-20 | 7.5 HIGH | N/A |
| Buffer overflow in Pico Server (pServ) 2.0 beta 1 through beta 5 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via (1) a 1024-byte TCP stream message, which triggers an off-by-one buffer overflow, or (2) a long method name in an HTTP request, (3) a long version number in an HTTP request, (4) a long User-Agent header, or (5) a long file path. | |||||