Suricata ja4: invalid alpn leads to panic
Published Oct 16, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Suricata ja4: invalid alpn leads to panic
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to version 7.0.7, invalid ALPN in TLS/QUIC traffic when JA4 matching/logging is enabled can lead to Suricata aborting with a panic. This issue has been addressed in 7.0.7. One may disable ja4 as a workaround.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- https://redmine.openinfosecfoundation.org/issues/7267 ↗
- www.vicarius.io ↗
- www.vicarius.io ↗
Record history
Published Oct 16, 2024 · Last refreshed Nov 3, 2026