CVE-2024-3393
A Denial of Service vulnerability in the DNS Security feature of Palo Alto Networks PAN-OS software allows an unauthenticated attacker to send a malicious packet through the data plane of the firewall that reboots the firewall. Repeated attempts to trigger this condition will cause the firewall to enter maintenance mode.
do firstUpgrade to a fixed release: >= 10.2.0 and < 10.2.8.
Can a WAF block it? No. The attack is performed by sending a malicious packet through the firewall's data plane using the DNS Security feature, which is not an HTTP-based request. Such packets do not have a distinct pattern that a web application firewall could reliably detect without blocking legitimate traffic.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-3393 being exploited?
Yes. CVE-2024-3393 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-3393?
CVE-2024-3393 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-3393?
Yes. A fix has been recorded for CVE-2024-3393. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-3393 affect?
CVE-2024-3393 affects paloaltonetworks:pan-os, paloaltonetworks:prisma_access. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 11.2.0 and < 11.2.3
- affected>= 11.1.0 and < 11.1.2-h16
- affected>= 10.2.8 and < 10.2.8-h19
- affected>= 10.1.14 and < 10.1.14-h8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 9 Jan 2025 (SSVC 2.0.3).
timeline
- 27 Dec 2024Published
- 30 Dec 2024Added to CISA KEV (exploited in the wild) · 3 days later
- 9 Jan 2025CISA SSVC assessment: exploitation active · 11 days later
- 20 Jan 2025CISA remediation due date (US federal agencies) · 10 days later
- 21 Oct 2025CVE record last updated · 275 days (about 9 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisorysecurity.paloaltonetworks.com /CVE-2024-3393
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-3393
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.