Skip to content
Fencer Vulns
high 7.5

CVE-2002-2295 json

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…

published 2002-12-31 23 y ago modified 2026-06-16 4 mo ago also EUVD-2002-2273

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.7%
EPSS 6.7% chance of exploitation in 30 days, percentile 93%
public exploits
1
Exploit-DB

Summary

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.

Timeline

  1. First public exploit (EDB-22056)
  2. Published

Exploit prediction

6.69% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-22056 Pserv 2.0 - HTTP Version Specifier Buffer Overflow dos, 2002-11-30
  • securiteam.com http://www.securiteam.com/securitynews/6Q0020A6AS.html referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/6285 referenced PoC, tagged "exploit" by a source, unverified
  • derkeiler.com http://www.derkeiler.com/Mailing-Lists/Full-Disclosure/2002-11/0457.html referenced PoC, tagged "exploit" by a source, unverified
  • derkeiler.com http://www.derkeiler.com/Mailing-Lists/securityfocus/bugtraq/2002-12/0005.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.