CVE-2025-64330
BaseFortify
Publication date: 2025-11-26
Last updated on: 2025-12-05
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oisf | suricata | to 7.0.13 (exc) |
| oisf | suricata | From 8.0.0 (inc) to 8.0.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a single byte read heap overflow in Suricata versions prior to 7.0.13 and 8.0.2. It occurs when logging the verdict in eve.alert and eve.drop records if the per packet alert queue is filled with alerts followed by a pass rule. This overflow can lead to crashes of the Suricata engine.
How can this vulnerability impact me? :
The vulnerability can cause Suricata to crash, potentially disrupting network intrusion detection and prevention operations. This could lead to loss of monitoring and protection capabilities, increasing the risk of undetected network attacks or intrusions.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Suricata to version 7.0.13 or 8.0.2 or later where the vulnerability is patched. Additionally, increase the alert queue size by adjusting the 'packet-alert-max' setting in the suricata.yaml configuration file if verdict logging is enabled.