CVE-2024-3400
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 command injection as a result of arbitrary file creation vulnerability in the GlobalProtect feature of Palo Alto Networks PAN-OS software for specific PAN-OS versions and distinct feature configurations may enable an unauthenticated attacker to execute arbitrary code with root privileges on the firewall. Cloud NGFW, Panorama appliances, and Prisma Access are not impacted by this vulnerability.
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 confidenceThis is a critical command injection vulnerability in the GlobalProtect feature of PAN-OS software. An unauthenticated attacker can exploit arbitrary file creation to achieve remote code execution with root privileges on affected firewalls. The vulnerability affects specific PAN-OS versions when GlobalProtect is enabled.
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= 10.2.0= 10.2.1= 10.2.2= 10.2.3= 10.2.4= 10.2.5= 10.2.6= 10.2.7= 10.2.8= 10.2.9= 11.0.0= 11.0.1CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 installed PAN-OS versionAccess the PAN-OS management interface or CLI and run 'show system info' or check the Dashboard for the system versionAffected if The installed version matches 10.2.0 through 10.2.9, 11.0.0, or 11.0.1 exactly
-
Confirm GlobalProtect feature statusNavigate to Network > GlobalProtect or run 'show global-protect' in the CLI to verify whether GlobalProtect is enabledAffected if GlobalProtect is enabled and actively serving connections
-
Verify GlobalProtect gateway configurationCheck Network > GlobalProtect > Gateways to see if any gateways are configured and operationalAffected if At least one GlobalProtect gateway is configured and running
-
Inspect GlobalProtect interface exposureReview the network configuration to determine if the GlobalProtect portal/gateway is accessible from untrusted networks (typically ports 443, 4443)Affected if The GlobalProtect interface is exposed to the internet or untrusted networks without adequate filtering
A system is affected if it runs PAN-OS version 10.2.0-10.2.9, 11.0.0, or 11.0.1 AND has GlobalProtect enabled and accessible to potential attackers.
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 · scopedUpgrade PAN-OS to the vendor-provided fixed versions. If immediate patching is not possible, consider disabling GlobalProtect or implementing compensating controls such as restricting GlobalProtect access to trusted sources via firewall policies.
PAN-OS 10.2.4 or later (verify latest available 10.2.x LTS or current stable release)
- 1. Identify the current PAN-OS version by navigating to Device > Setup > Operations or using 'show system info' in the CLI
- 2. Confirm if GlobalProtect is enabled on the firewall (this vulnerability only affects systems with GlobalProtect configured)
- 3. Download the fixed PAN-OS version from the Palo Alto Networks Customer Support Portal
- 4. Upload the new PAN-OS image to the firewall via Panorama or directly to the device
- 5. Schedule a maintenance window and install the update, following Palo Alto Networks upgrade best practices
- 6. After upgrade, verify the PAN-OS version matches the fixed release and confirm GlobalProtect functionality
- 7. Review system logs to ensure no compromise occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.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,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3400 — 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-3400 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