Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 20 Jan 2025.
Pan OsOperating system · Paloaltonetworks

CVE-2024-3393

HIGH · 7.5 CVSS v3.1 Published 2024-12-27
Fix available
A fix is available. Upgrade to 11.2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · high confidence

A Denial of Service vulnerability exists in the DNS Security feature of Palo Alto Networks PAN-OS software. An unauthenticated attacker can send a malicious packet through the firewall's data plane causing an immediate reboot. Repeated exploitation will cause the firewall to enter maintenance mode.

MitigationApply the vendor-supplied PAN-OS security update when available. As a temporary workaround, consider disabling the DNS Security feature if operationally feasible, or implement network-level filtering to limit exposure to untrusted traffic sources.

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
Pan OsOperating system
Affected:>= 11.1.0, <= 11.1.1>= 11.2.0, < 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 AccessApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the PAN-OS version
    Run 'show system info' on the firewall CLI or check via Panorama under Device > Setup > Operations > Device Information
    Affected if The version matches any of these ranges: 11.1.0 to 11.1.1, 11.2.0 to 11.2.2, 10.1.14, 10.2.8 to 10.2.13, 11.1.2 to 11.1.4, or any Prisma Access version
  2. Confirm DNS Security is enabled
    Navigate to Objects > DNS Security in the web UI or run 'show dns-security' in the CLI to check if the DNS Security service is active
    Affected if DNS Security feature is turned on or any DNS Security policies are configured
  3. Check for DNS Security policy rules
    Review Policies > DNS Security in the web UI or run 'show dns-security policy' to list any active DNS Security policies
    Affected if Any DNS Security policies exist that process DNS traffic through the firewall
  4. Verify external exposure
    Review the firewall interface configuration and security zone assignments to determine if interfaces facing untrusted networks (such as internet-facing interfaces) are permitted to process DNS traffic
    Affected if The firewall has interfaces with exposed DNS Security processing to untrusted or external networks

You are affected if your PAN-OS version is in the affected list (or any Prisma Access version) AND DNS Security is enabled or configured on the firewall.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.2.3 or later
Fixed in 11.2.3
Interim mitigation

Apply the vendor-supplied PAN-OS security update when available. As a temporary workaround, consider disabling the DNS Security feature if operationally feasible, or implement network-level filtering to limit exposure to untrusted traffic sources.

Recommended fix High confidence

PAN-OS 11.2.3 or later (for 11.2.x line); PAN-OS 11.1.2 or later (for 11.1.x line); PAN-OS 10.2.9 or later (for 10.2.x line); PAN-OS 10.1.15 or later (for 10.1.x line); latest Prisma Access version

  1. 1. Identify the current PAN-OS or Prisma Access version running on the device
  2. 2. For PAN-OS 11.1.x: Upgrade to PAN-OS 11.1.2 or later
  3. 3. For PAN-OS 11.2.x: Upgrade to PAN-OS 11.2.3 or later
  4. 4. For PAN-OS 10.1.x: Upgrade to a version newer than 10.1.14 (e.g., 10.1.15 or later)
  5. 5. For PAN-OS 10.2.x: Upgrade to a version newer than 10.2.8 (e.g., 10.2.9 or later)
  6. 6. For Prisma Access: Apply the latest Prisma Access version per Palo Alto Networks guidance
  7. 7. After upgrade, verify the DNS Security feature is functioning correctly
  8. 8. Monitor for any unexpected firewall behavior
Caveat Review Palo Alto Networks release notes for any configuration or feature changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pan Os Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3393 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3393 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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