CVE-2024-47522
Suricata ja4: invalid alpn leads to panic
In short
Suricata crashes when it encounters invalid ALPN (Application Layer Protocol Negotiation) data in TLS/QUIC traffic while JA4 fingerprinting is enabled. This causes the security monitoring tool to stop working, disrupting network protection.
Technical detail
A malformed ALPN extension in TLS/QUIC handshakes triggers a panic in Suricata's JA4 matching logic, causing process termination. The attack requires only network-level access to send crafted TLS/QUIC packets; no authentication or special conditions are needed. Impact is denial of service to the monitoring infrastructure.
Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
OISF · suricataWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://github.com/OISF/suricata/security/advisories/GHSA-w5xv-6586-jpm7https://redmine.openinfosecfoundation.org/issues/7267https://www.vicarius.io/vsociety/posts/cve-2024-47522-detect-suricata-vulnerabilityhttps://www.vicarius.io/vsociety/posts/cve-2024-47522-mitigate-suricata-vulnerability