CVE-2024-3393
Palo Alto Networks PAN-OS Malicious DNS Packet Vulnerability
Palo Alto Networks PAN-OS
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 30 December 2024. US federal agencies were required to remediate it by 20 January 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 29.1%, which is higher than 98.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Frequently asked questions
Is CVE-2024-3393 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-3393.
What does CVE-2024-3393 affect?
CVE-2024-3393 affects Palo Alto Networks PAN-OS. 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.
How severe is CVE-2024-3393?
CVE-2024-3393 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 29.1%, higher than 98.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 20 January 2025.
How should organisations respond to CVE-2024-3393?
Apply the vendor patch for Palo Alto Networks PAN-OS as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.