CVE-2024-47522
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSuricata 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn Suricata versions prior to 7.0.7, the JA4 fingerprinting feature does not properly handle invalid Application-Layer Protocol Negotiation (ALPN) values in TLS/QUIC traffic, causing the engine to panic and abort. This creates a denial-of-service condition when processing specially crafted traffic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.0.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Suricata installed versionRun 'suricata --version' or check the package manager for the installed Suricata versionAffected if The version shown is less than 7.0.7 (for example, 7.0.6, 7.0.5, 7.0.4, etc.)
-
Locate Suricata configuration fileFind the suricata.yaml configuration file, typically in /etc/suricata/ or the directory where Suricata was installedAffected if The configuration file exists and JA4 settings can be inspected
-
Verify JA4 fingerprinting is enabledSearch for 'ja4' in the configuration file (look for 'ja4-fingerprints' or similar JA4-related settings) and confirm they are set to 'enabled' or 'true'Affected if JA4 fingerprinting is explicitly enabled in the configuration (note: if JA4 is disabled, the vulnerability cannot be triggered)
You are affected if Suricata version is below 7.0.7 AND JA4 fingerprinting is enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.7
Upgrade to Suricata 7.0.7 or disable the ja4 feature in the configuration as a workaround to prevent the panic.
Suricata 7.0.7
- Identify your current Suricata installation method (e.g., package manager, source compilation, Docker)
- For package manager installations: Update your package repository and upgrade Suricata to version 7.0.7 or later
- For source compilation: Download and compile Suricata 7.0.7 or later from the official repository
- For Docker: Pull the Suricata 7.0.7 or later image
- After upgrade, verify the Suricata version matches 7.0.7 or higher using 'suricata --version'
- Test that Suricata starts successfully and processes traffic without panics
- If upgrade is not immediately possible, disable JA4 functionality by setting 'ja4-fingerprints: no' in your suricata.yaml configuration as a workaround
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47522 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47522 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data