IRONSMITHINTEL
HIGHCVSS7.5
|
Actively Exploited
|CISA KEV|CVE-2024-3393|Auth: none — unauthenticated|Reboot: required|Manual only

Palo Alto Networks PAN-OS Malicious DNS Packet Vulnerability (CVE-2024-3393)

Palo Alto Networks PAN-OS contains a vulnerability in parsing and logging malicious DNS packets in the DNS Security feature that, when exploited, allows an unauthenticated attacker to remotely reboot the firewall. Repeated attempts to trigger this condition will cause the firewall to enter maintenance mode.

Published Dec 27, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve partial data exposure, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-01-20 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-754) (CWE-754) vulnerability in 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 requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

Network Security Team
Firewall Administrators
IT Security
Running pan-os: 11.1.0 ≤ v ≤ 11.1.1, 11.2.0 ≤ v < 11.2.3, 10.1.14, 10.2.8, 10.2.9, 10.2.10, 10.2.11, 10.2.12, 10.2.13, 11.1.2, 11.1.3, 11.1.4; prisma access: -
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2024-12-30 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-01-20.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2024-3393's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.