CVE-2024-47522 json
Suricata ja4: invalid alpn leads to panic
published 2y ago modified 4mo ago also EUVD-2024-42513
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- oisf suricata 7.0.7
- openinfosecfoundation suricata 7.0.7
- suricata-ids suricata 7.0.7
- suricata Debian 14, Debian 13 1:7.0.7-1
debian advisories DEBIAN-CVE-2024-47522
- suricata openSUSE Tumbleweed 8.0.0-1.1
opensuse advisories openSUSE-SU-2025:15394-1
- suricata Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 7.0.7-r0
alpine advisories ALPINE-CVE-2024-47522
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2024-47522 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-47522 updated
suricata: Suricata ja4: invalid alpn leads to panic
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- OISF suricata
Classification
- Weakness
-
- CWE-617 Reachable Assertion
References
-
redmine.openinfosecfoundation.org
/issues/7267
issue-tracking, vendor-advisory
-
github.com
/OISF/suricata/security/advisories/GHSA-w5xv-6586-jpm7
mitigation, third-party-advisory
- vicarius.io /vsociety/posts/cve-2024-47522-detect-suricata-vulnerability
- vicarius.io /vsociety/posts/cve-2024-47522-mitigate-suricata-vulnerability
Sources
- CVE List CVE-2024-47522
- NVD CVE-2024-47522
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.