CVE-2024-3384
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 · uneditedA vulnerability in Palo Alto Networks PAN-OS software enables a remote attacker to reboot PAN-OS firewalls when receiving Windows New Technology LAN Manager (NTLM) packets from Windows servers. Repeated attacks eventually cause the firewall to enter maintenance mode, which requires manual intervention to bring the firewall back online.
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 confidenceA vulnerability in PAN-OS allows remote attackers to cause denial of service by sending crafted Windows NTLM packets to firewalls, triggering repeated reboots that eventually force the device into maintenance mode requiring manual intervention to recover.
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>= 8.1.0, < 8.1.24>= 9.0.0, < 9.0.17>= 9.1.0, < 9.1.15>= 10.0.0, < 10.0.12= 9.1.15CVSS 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.
-
Determine installed PAN-OS versionRun 'show system info' from the CLI or check System Information in the web management interface under Device > Setup > OperationsAffected if The version displayed is 8.1.0 to 8.1.23, 9.0.0 to 9.0.16, 9.1.0 to 9.1.14, or 10.0.0 to 10.0.11 (these fall within the vulnerable ranges)
-
Identify interfaces accepting NTLM trafficReview firewall interface configurations and security policies to determine which interfaces can receive NTLM authentication traffic from untrusted sourcesAffected if Any management or data interface is configured to accept NTLM authentication requests from external or untrusted networks
You are affected if your PAN-OS version falls within any of the vulnerable version ranges AND your firewall is reachable by attackers sending crafted NTLM packets from untrusted network segments.
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 · scoped8.1.249.0.179.1.15
Apply the vendor-supplied patch or upgrade to a fixed PAN-OS version; consider network segmentation to limit exposure of firewalls to untrusted NTLM traffic sources.
Upgrade to PAN-OS 8.1.24, 9.0.17, 9.1.15, or 10.0.12 (or later stable releases within each respective branch)
- 1. Determine the current PAN-OS version by accessing the firewall management interface or running 'show system info' in the CLI.
- 2. Identify which version branch (8.1, 9.0, 9.1, or 10.0) the firewall is currently running.
- 3. Download the appropriate fixed PAN-OS version from the Palo Alto Networks Support Portal: version 8.1.24 or higher for 8.1 branch, 9.0.17 or higher for 9.0 branch, 9.1.15 or higher for 9.1 branch, or 10.0.12 or higher for 10.0 branch.
- 4. Upload the PAN-OS upgrade file to the firewall via the web interface (Device > Software) or SCP.
- 5. Schedule a maintenance window as upgrades require a reboot.
- 6. Install the upgrade and reboot the firewall.
- 7. Verify the upgrade was successful by checking the PAN-OS version after reboot.
- 8. Test firewall functionality and connectivity to ensure normal operation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3384 — 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-3384 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