Memory exhaustion via oversized decode_base64 bytes setting
Published Apr 10, 2025 · Updated Apr 11, 2025
Uncontrolled resource allocation in Suricata before 7.0.9 allows local users to starve memory through an untrusted decode_base64 rule. The decode_base64 parser accepts a bytes value as a 32-bit unsigned integer and sizes the per-thread decoded-data buffer from the largest configured value, permitting an allocation approaching 4 GiB for each thread. Loading an attacker-supplied signature containing an oversized value is required, and the resulting resource starvation can interrupt the detection engine without disclosing or altering data.
Summary
What happened
Uncontrolled resource allocation in Suricata before 7.0.9 allows local users to starve memory through an untrusted decode_base64 rule. The decode_base64 parser accepts a bytes value as a 32-bit unsigned integer and sizes the per-thread decoded-data buffer from the largest configured value, permitting an allocation approaching 4 GiB for each thread. Loading an attacker-supplied signature containing an oversized value is required, and the resulting resource starvation can interrupt the detection engine without disclosing or altering data.
The record
- CVE
- CVE-2025-29917
- Published
- Apr 10, 2025
- Updated
- Apr 11, 2025
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-770, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2025CVE publishedPublication date reported by the CVE source.
- Apr 11, 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=< 7.0.9
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