CVE-2025-59150
BaseFortify
Publication date: 2025-10-01
Last updated on: 2025-10-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oisf | suricata | 8.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Suricata version 8.0.0 occurs when using the tls.subjectaltname keyword. If the decoded subjectaltname contains a NULL byte, it can cause a segmentation fault, leading to a crash or instability in the system. This issue is resolved in version 8.0.1, and a temporary workaround is to disable rules that use the tls.subjectaltname keyword.
How can this vulnerability impact me? :
The vulnerability can cause Suricata to crash or become unstable due to a segmentation fault when processing certain TLS subject alternative names containing NULL bytes. This can lead to denial of service (DoS) conditions, impacting network monitoring and security operations.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should disable rules using the tls.subjectaltname keyword in Suricata version 8.0.0, or upgrade to Suricata version 8.0.1 where the issue is fixed.