Remote engine crash via unanchored entropy rule
Published Oct 1, 2025 · Updated Oct 1, 2025
NULL pointer dereference in Suricata 8.0.0 allows remote attackers to crash the engine through traffic matching an unanchored entropy rule. DetectEntropyDoMatch stores the computed value with FlowVarAddFloat through det_ctx->p->flow without checking that a flow exists for an unanchored content buffer. Exploitation requires an enabled local rule with an unanchored entropy keyword and matching network traffic, and a successful trigger terminates packet inspection.
Summary
What happened
NULL pointer dereference in Suricata 8.0.0 allows remote attackers to crash the engine through traffic matching an unanchored entropy rule. DetectEntropyDoMatch stores the computed value with FlowVarAddFloat through det_ctx->p->flow without checking that a flow exists for an unanchored content buffer. Exploitation requires an enabled local rule with an unanchored entropy keyword and matching network traffic, and a successful trigger terminates packet inspection.
The record
- CVE
- CVE-2025-59148
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo