Skip to content
Fencer Vulns
medium 6.2

CVE-2024-2397 json

infinite loop in the PPP printer of tcpdump

published 2024-04-12 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-27349

cvss
6.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

Due to a bug in packet data buffers management, the PPP printer in tcpdump can enter an infinite loop when reading a crafted DLT_PPP_SERIAL .pcap savefile. This problem does not affect any tcpdump release, but it affected the git master branch from 2023-06-05 to 2024-03-21.

Patch / fix

  • tcpdump openSUSE Tumbleweed 4.99.5-1.1

opensuse advisories openSUSE-SU-2024:14305-1

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-2024-2397 updated cvss 5.5

tcpdump: Crafted .pcap file may lead to Denial of Service

  • Red Hat Enterprise Linux 6 libpcap, tcpdump Red Hat Enterprise Linux 7 libpcap, tcpdump
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 tcpdump Red Hat Enterprise Linux 9 tcpdump
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 libpcap Red Hat Enterprise Linux 9 libpcap Red Hat Enterprise Linux 10 libpcap, tcpdump
    not affected: vulnerable code not present

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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • The Tcpdump Group tcpdump

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

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.