CVE-2024-28870
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSuricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine developed by the OISF and the Suricata community. When parsing an overly long SSH banner, Suricata can use excessive CPU resources, as well as cause excessive logging volume in alert records. This issue has been patched in versions 6.0.17 and 7.0.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSuricata's SSH banner parsing logic contains a vulnerability where overly long SSH banners trigger excessive CPU consumption and generate excessive logging volume in alert records. This can be exploited to cause denial-of-service conditions through resource exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.0.17>= 7.0.0, < 7.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Suricata versionRun 'suricata --version' or check the package manager (dpkg -l suricata, rpm -qi suricata)Affected if Version is below 6.0.17, or between 7.0.0 and 7.0.4 (exclusive)
-
Verify SSH parsing is enabled in SuricataInspect the Suricata configuration file (typically /etc/suricata/suricata.yaml) for 'app-layer' settings and ensure ssh.parser is not disabled, or check if ssh protocol is being parsed in the rules/flow configurationAffected if SSH protocol parsing is enabled and the version falls in the affected range
-
Confirm Suricata is actively processing SSH trafficCheck if there are active SSH flows or if the SSH banner parser is being invoked - look at Suricata logs or run 'suricata --list-app-layer-protos' to confirm SSH support is compiled inAffected if Suricata is actively inspecting SSH traffic and version is affected
You are affected if Suricata is parsing SSH traffic and the installed version is below 6.0.17 or between 7.0.0 and 7.0.4.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.0.177.0.4
Upgrade Suricata to version 6.0.17 or 7.0.4 which contain the patch for this vulnerability. If immediate upgrade is not feasible, consider implementing network-level filtering or rate limiting for SSH connections with unusually long banners.
Suricata 6.0.17 (for 6.x branch) or 7.0.4 (for 7.x branch)
- 1. Identify the currently installed Suricata version using 'suricata --version'
- 2. If running Suricata 6.x series (version < 6.0.17), plan upgrade to version 6.0.17
- 3. If running Suricata 7.x series (>= 7.0.0 and < 7.0.4), plan upgrade to version 7.0.4
- 4. Consult the official Suricata upgrade documentation for your installation method (e.g., package manager, source compilation)
- 5. Before upgrading, backup Suricata configuration files (/etc/suricata/ by default)
- 6. Upgrade Suricata using your package manager or by compiling from source
- 7. Verify the new version is running using 'suricata --version'
- 8. Test that SSH traffic is being parsed correctly and that the resource issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28870 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data