VulnerabilityPublished 16 Oct 2024Updated 2 Apr 2026

CVE-2024-45796: OISF suricata · Off-by-one Error

Affects OISF suricataSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 7.0.7 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

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

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

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

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

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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Upgrade oisf/suricata to 7.0.7.

Affected software

Product	Affected	Fixed in
GitHuboisf/suricata`pkg:github/oisf/suricata`Other threats	Affected <7.0.7	Fixed in 7.0.7

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-45796, organizations should upgrade Suricata to version 7.0.7 or later, where the off-by-one error in fragment reassembly has been fixed. Prior to upgrading, network administrators should audit their Suricata deployment versions and identify any instances running vulnerable releases. In environments where immediate upgrading is not feasible, consider implementing additional network-level protections such as strict packet filtering or limiting exposure of Suricata sensors to untrusted networks. Monitoring network traffic for anomalous fragmentation patterns may help detect attempts to exploit this vulnerability. Regularly review Suricata logs and alerts for signs of evasion or suspicious fragmented packets. Employ defense-in-depth strategies by combining Suricata with other security controls like firewalls and endpoint detection to reduce reliance on a single detection mechanism. Stay informed about any emerging exploit reports or patches related to this vulnerability. Finally, conduct thorough testing of Suricata updates in staging environments to ensure stability and compatibility before production deployment.

Description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to version 7.0.7, a logic error during fragment reassembly can lead to failed reassembly for valid traffic. An attacker could craft packets to trigger this behavior.This issue has been addressed in 7.0.7.

Impact

The primary impact of CVE-2024-45796 is on the integrity of network security monitoring performed by Suricata. By exploiting the off-by-one error in fragment reassembly, attackers can craft fragmented packets that Suricata fails to properly reassemble and inspect. This can allow malicious traffic to evade detection, potentially enabling network intrusions, data exfiltration, or the delivery of malware without triggering alerts. Organizations relying on Suricata for intrusion detection or prevention may have blind spots in their network visibility, increasing the risk of undetected attacks. While the vulnerability does not directly compromise confidentiality or availability, the loss of detection capability can indirectly lead to more severe security incidents. The ease of remote exploitation without authentication increases the threat level, especially in environments with high network exposure. The lack of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks. Organizations with critical infrastructure, sensitive data, or compliance requirements are particularly at risk if they do not update to the patched version.

CWE-193Off-by-one Error (opens in a new tab)
Base weakness
A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.
Implementation
When copying character arrays or using character manipulation methods, the correct size parameter must be used to account for the null terminator that needs to be added at the end of the array.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 03:25 UTC

WeaknessesCWE-193

Technical details

References

Community reviews

Related threats