CVE-2024-22654VulnerabilityPublished 29 May 2025Updated 30 May 2025

CVE-2024-22654: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubappneta/tcpreplay`pkg:github/appneta/tcpreplay`Other threats	Affected =4.4.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-22654, European organizations should first identify all instances of tcpreplay version 4.4.4 or earlier in their environments. In the interim, restricting access to systems running tcpreplay to trusted personnel and networks can reduce exposure. Implement input validation and sanitization on packet capture files used with tcpreplay to avoid malformed or maliciously crafted data that could trigger the infinite loop. Consider running tcpreplay in isolated or sandboxed environments to contain potential denial of service impacts. Additionally, incorporate monitoring and alerting for unusual resource consumption or process hangs related to tcpreplay executions. Network teams should also evaluate alternative packet replay tools that do not exhibit this vulnerability until a fix is released. Finally, maintain regular backups and incident response plans to quickly recover from any service disruptions caused by exploitation attempts.

Description

tcpreplay v4.4.4 was discovered to contain an infinite loop via the tcprewrite function at get.c.

Impact

For European organizations, the primary impact of CVE-2024-22654 is a denial of service condition affecting systems that utilize tcpreplay for network testing, security research, or forensic analysis. Organizations relying on tcpreplay to simulate network traffic for intrusion detection system (IDS) tuning, firewall testing, or network performance evaluation may experience service interruptions or delays if the vulnerability is exploited. This could disrupt security operations centers (SOCs) or network engineering teams, potentially delaying incident response or network troubleshooting activities. While the vulnerability does not compromise data confidentiality or integrity, the availability impact could hinder critical security validation processes. Given the remote exploitability without authentication or user interaction, attackers could cause tcpreplay-based services or automated testing environments to become unresponsive, impacting operational efficiency. However, since tcpreplay is a specialized tool primarily used by network professionals rather than general production environments, the overall risk to broad enterprise infrastructure is limited. The absence of known exploits in the wild reduces immediate threat levels but does not eliminate the risk of future exploitation, especially in targeted attacks against organizations with mature network testing capabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 20:55 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats