Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-55628 is a high-severity Amplification (CWE-405) vulnerability in Oisf Suricata. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Denial of Service (T1498); ranked at the 50th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AU-2 (Event Logging) and AU-7 (Audit Record Reduction and Report Generation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-55628 affects Suricata, an open-source network Intrusion Detection System (IDS), Intrusion Prevention System (IPS), and Network Security Monitoring (NSM) engine. In versions prior to 7.0.8, the vulnerability stems from improper handling of DNS resource name compression, where small DNS messages can encode very large hostnames. This results in excessive computational costs during decoding and the generation of oversized DNS log records. Existing limits on hostname lengths were deemed too permissive, earning a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and mapping to CWE-405 (Asymmetric Resource Consumption), CWE-779 (Logging of Excessive Data), and NVD-CWE-Other.
A remote, unauthenticated attacker can exploit this flaw by sending specially crafted DNS packets over the network. The decompression process consumes disproportionate resources, potentially leading to denial-of-service conditions through CPU exhaustion or disk space depletion from massive log entries. No user interaction or privileges are required, making it feasible against internet-exposed Suricata deployments performing DNS inspection.
The issue was addressed in Suricata version 7.0.8 via targeted commits tightening hostname length limits and improving decompression bounds. Official advisories, including GHSA-96w4-jqwf-qx2j on GitHub and Open Information Security Foundation's Redmine ticket #7280, recommend upgrading to 7.0.8 or later. Relevant patches are available in commits such as 19cf0f81335d9f787d587450f7105ad95a648951, 37f4c52b22fcdde4adf9b479cb5700f89d00768d, and 3a5671739f5b25e5dd973a74ca5fd8ea40e1ae2d.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52826
Vulnerability Data
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to version 7.0.8, DNS resource name compression can lead to small DNS messages containing very large hostnames which can be costly to decode, and…
more
lead to very large DNS log records. While there are limits in place, they were too generous. The issue has been addressed in Suricata 7.0.8.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Defining the exact event types to be logged prevents indiscriminate collection of excessive data.
Audit-record reduction and on-demand reporting directly reduce the impact of overly verbose logs during review.
SC-5 directly requires mechanisms to limit the effects of asymmetric resource exhaustion attacks such as amplification DoS.
SC-6 enforces resource quotas and priority allocation that reduce the impact of unauthenticated or low-effort resource requests.
Least-functionality disables unnecessary services or features that could be leveraged for amplification.
SC-7 boundary controls can filter or rate-limit traffic patterns that enable amplification without equivalent client work.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Excessive logging hinders log processing and forensic analysis, largely undermining DE.AE-04's ability to estimate impact/scope via SIEMs or tools while removing most of that outcome's efficacy.
Resilience mechanisms such as rate limiting and load balancing directly constrain asymmetric resource use.
Capacity planning and monitoring maintain availability headroom against amplification attacks.
Excessive logging undermines event analysis by flooding logs with noise that hinders processing and forensic review, but does not blind or defeat the outcome the way insufficient logging would.
Excessive logging impairs processing of provided event data and log-analysis findings (one aspect of DE.AE-06) without fully defeating alert/ticket distribution.
Network monitoring detects amplification traffic patterns but does not itself limit asymmetric consumption.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.15 directly requires logging to be configured so that only necessary events are recorded, preventing excessive data.
Documented operating procedures can include logging guidelines, indirectly reducing excessive logging.
Monitoring activities can detect excessive logging but do not prescribe how much data should be logged.
Stress-testing and demand-reduction tactics (e.g., bandwidth throttling) blunt amplification vectors that would otherwise let an attacker multiply resource consumption through a single request.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248553 OL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-405
- V-248552 OL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-405
Oracle Linux 9 (2 rules)
- V-271709 OL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-405
- V-271710 OL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-405
RHEL 8 (2 rules)
- V-230244 RHEL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-405
- V-244525 RHEL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-405