CVE-2024-3385
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 packet processing mechanism in Palo Alto Networks PAN-OS software enables a remote attacker to reboot hardware-based firewalls. Repeated attacks eventually cause the firewall to enter maintenance mode, which requires manual intervention to bring the firewall back online. This affects the following hardware firewall models: - PA-5400 Series firewalls - PA-7000 Series firewalls
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 the packet processing mechanism of PAN-OS software allows remote attackers to send specially crafted packets that cause hardware-based firewalls (PA-5400 and PA-7000 Series) to reboot. Repeated exploitation can trigger maintenance mode, requiring manual intervention for recovery.
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>= 9.0.0, <= 9.0.16>= 9.1.0, < 9.1.17>= 10.1.0, < 10.1.12>= 10.2.0, < 10.2.8>= 11.0.0, < 11.0.3= 9.0.17CVSS 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.
-
Identify the hardware modelRun 'show system info' or access the device dashboard to confirm the model is a PA-5400 or PA-7000 Series firewallAffected if The device is a PA-5400 or PA-7000 Series hardware appliance - only these models are affected
-
Check the PAN-OS versionRun 'show system info' or 'request system software info' to retrieve the installed PAN-OS versionAffected if The installed version falls within: 9.0.0-9.0.16, 9.1.0-9.1.16, 10.1.0-10.1.11, 10.2.0-10.2.7, 11.0.0-11.0.2, or equals 9.0.17
-
Verify network exposure of the firewallReview interface configurations and access policies to determine if the firewall can receive specially crafted packets from untrusted networksAffected if The firewall data plane or management interface is directly accessible from untrusted networks without adequate filtering or rate limiting
You are affected if you run a PA-5400 or PA-7000 Series firewall with PAN-OS version 9.0.0-9.0.16, 9.1.0-9.1.16, 10.1.0-10.1.11, 10.2.0-10.2.7, 11.0.0-11.0.2, or 9.0.17, and the device is network-accessible to potential attackers sending crafted packets.
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 · scoped9.1.1710.1.1210.2.8
Apply the vendor-supplied PAN-OS update for this vulnerability. Implement network-level filtering or rate limiting to reduce attack surface until the patch can be deployed. Plan maintenance windows for affected hardware firewalls given the manual recovery requirement.
PAN-OS 9.0.17+, 9.1.17+, 10.1.12+, or 10.2.8+ (migration to newer branches like 10.2 or 11.0 recommended)
- 1. Identify the current PAN-OS version running on the affected firewall (PA-5400 Series or PA-7000 Series) using the web interface or CLI command 'show system info'
- 2. Determine which version branch the current installation belongs to (9.0.x, 9.1.x, 10.1.x, or 10.2.x)
- 3. Download the appropriate PAN-OS upgrade image from the Palo Alto Networks Customer Support Portal
- 4. For PAN-OS 9.0.x: upgrade to PAN-OS 9.0.17 or later (note: 9.0 is End-of-Life, consider upgrading to a supported branch)
- 5. For PAN-OS 9.1.x: upgrade to PAN-OS 9.1.17 or later (note: 9.1 is End-of-Life, consider upgrading to a supported branch)
- 6. For PAN-OS 10.1.x: upgrade to PAN-OS 10.1.12 or later
- 7. For PAN-OS 10.2.x: upgrade to PAN-OS 10.2.8 or later
- 8. Upload the upgrade file via Panorama or directly to the firewall
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3385 — 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-3385 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