CVE-2024-45795
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. Prior to version 7.0.7, rules using datasets with the non-functional / unimplemented "unset" option can trigger an assertion during traffic parsing, leading to denial of service. This issue is addressed in 7.0.7. As a workaround, use only trusted and well tested rulesets.
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 · high confidenceSuricata versions prior to 7.0.7 contain a denial-of-service vulnerability where rules utilizing datasets with the unimplemented 'unset' option trigger an assertion failure during traffic parsing, causing the intrusion detection engine to crash.
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< 7.0.7CVSS 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 for the installed versionAffected if Version is earlier than 7.0.7
-
Locate active ruleset filesFind the rules files loaded by Suricata - typically in /etc/suricata/rules/ or as configured in suricata.yaml under 'rule-files'Affected if Rules files exist and are loaded by Suricata
-
Search for dataset 'unset' option in rulesUse grep to search for the pattern 'dataset:set;unset' or 'unset' within dataset rules in the active ruleset filesAffected if Any rule contains the 'unset' option in a dataset declaration (e.g., 'dataset:set;unset')
-
Verify rule is loaded and activeCheck suricata.log or run 'suricata --list-debug' to confirm the problematic rule is actually loaded by the engineAffected if The rule with 'unset' dataset option is loaded and active in the running configuration
Environment is affected if Suricata version is below 7.0.7 AND rules containing the unimplemented 'unset' dataset option are loaded and active.
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 · scoped7.0.7
Upgrade Suricata to version 7.0.7 or later. As a workaround, audit and remove rules containing the 'unset' dataset option, and only deploy trusted and well-tested rulesets.
Suricata 7.0.7
- 1. Back up current Suricata configuration and rulesets
- 2. Obtain Suricata version 7.0.7 from the official source (https://suricata.io/download/)
- 3. Upgrade Suricata to version 7.0.7 using your system's package manager or compile from source
- 4. Verify the installation succeeded by running 'suricata --version'
- 5. Test your rulesets to ensure they function correctly with the new version
- 6. Restart Suricata service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45795 — 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-45795 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