Skip to content
Fencer Vulns
high 7.5

CVE-2003-0213 in the critical feed json

ctrlpacket.c in PoPToP PPTP server before 1.1.4-b3 allows remote attackers to cause a denial of service via a length field of 0 or 1, which…

published 2003-04-26 23 y ago modified 2026-06-16 4 mo ago also EUVD-2003-0208

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

Summary

ctrlpacket.c in PoPToP PPTP server before 1.1.4-b3 allows remote attackers to cause a denial of service via a length field of 0 or 1, which causes a negative value to be fed into a read operation, leading to a buffer overflow.

Patch / fix

  • pptpd Debian 14, Debian 13, Debian 12 1.1.4-0.b3.2

debian advisories DEBIAN-CVE-2003-0213

Timeline

  1. First public exploit (Metasploit exploit/linux/pptp/poptop_negative_read)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/linux/pptp/poptop_negative_read Poptop Negative Read Overflow metasploit exploit, great rank, 2003-04-09
  • EDB-22479 PoPToP PPTP 1.0/1.1.x - Negative 'read()' Argument Remote Buffer Overflow remote, 2003-04-09
  • EDB-16845 PoPToP - Negative Read Overflow (Metasploit) remote, 2010-11-23
  • EDB-9952 PoPToP < 1.1.3-b3/1.1.3-20030409 - Negative Read Overflow (Metasploit) remote, 2003-04-09
  • EDB-19 PoPToP PPTP 1.1.4-b3 - 'poptop-sane.c' Remote Command Execution remote, 2003-04-25
  • EDB-16 PoPToP PPTP 1.1.4-b3 - Remote Command Execution remote, 2003-04-18
  • securityfocus.com http://www.securityfocus.com/bid/7316 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

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.