Skip to content
Fencer Vulns
medium 5.0

CVE-2004-0183 json

TCPDUMP 3.8.1 and earlier allows remote attackers to cause a denial of service (crash) via ISAKMP packets containing a Delete payload with…

published 2004-04-06 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0183

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.6%
EPSS 5.6% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

TCPDUMP 3.8.1 and earlier allows remote attackers to cause a denial of service (crash) via ISAKMP packets containing a Delete payload with a large number of SPI's, which causes an out-of-bounds read, as demonstrated by the Striker ISAKMP Protocol Test Suite.

Patch / fix

  • tcpdump Debian 14, Debian 13, Debian 12 3.7.2-4

debian advisories DEBIAN-CVE-2004-0183

  • tcpdump RHEL 3 14:3.7.2-7.E3.2
  • libpcap RHEL 3 14:0.7.2-7.E3.2

red hat advisories RHSA-2004:219

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2004-0183 updated

security flaw

  • Red Hat Desktop version 3 libpcap 0.7.2-7.E3.2, tcpdump 3.7.2-7.E3.2 Red Hat Enterprise Linux AS version 3 libpcap 0.7.2-7.E3.2, tcpdump 3.7.2-7.E3.2 Red Hat Enterprise Linux ES version 3 libpcap 0.7.2-7.E3.2, tcpdump 3.7.2-7.E3.2 Red Hat Enterprise Linux WS version 3 libpcap 0.7.2-7.E3.2, tcpdump 3.7.2-7.E3.2
    fixed: vendor fix RHSA-2004:219

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

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

Classification

Weakness

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.