# CVE-2024-3400: Palo Alto Networks PAN-OS Command Injection

> Unauthenticated attackers can execute arbitrary code with root privileges on PAN-OS firewalls via command injection in GlobalProtect.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 Apr 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-v475-xhc9-wfxg

## What is CVE-2024-3400?

CVE-2024-3400 is a critical command injection vulnerability in Paloaltonetworks Pan-Os, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-3400?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2024-3400?

No fix has been published for CVE-2024-3400 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Apr 2024.

## Is CVE-2024-3400 being exploited?

Yes. Attackers have exploited CVE-2024-3400 in the wild since at least 12 Apr 2024, including in ransomware campaigns.

Public exploit code:

- CVE-2024-3400 Palo Alto OS Command Injection (github_poc): https://github.com/h4x0r-dz/CVE-2024-3400
- CVE-2024-3400-RCE (github_poc): https://github.com/W01fh4cker/CVE-2024-3400-RCE-Scan
- CVE-2024-3400 (github_poc): https://github.com/0x0d3ad/CVE-2024-3400
- CVE-2024-3400 PAN-OS: OS Command Injection Vulnerability in GlobalProtect (github_poc): https://github.com/ihebski/CVE-2024-3400
- https://github.com/Chocapikk/CVE-2024-3400 (github_poc): https://github.com/Chocapikk/CVE-2024-3400
- https://github.com/momika233/CVE-2024-3400 (github_poc): https://github.com/momika233/CVE-2024-3400

## Other vulnerabilities in Paloaltonetworks Pan-Os

- [CVE-2020-2021](https://insights.sbomify.com/CVE-2020-2021/): Palo Alto Networks PAN-OS Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2017-15944](https://insights.sbomify.com/CVE-2017-15944/): Palo Alto Networks PAN-OS Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2026-0300](https://insights.sbomify.com/CVE-2026-0300/): Palo Alto Networks PAN-OS Out-of-bounds Write (critical 9.3, exploited in the wild)
- [CVE-2024-0012](https://insights.sbomify.com/CVE-2024-0012/): Palo Alto Networks PAN-OS Management Interface Authentication Bypass (critical 9.3, exploited in the wild)
- [CVE-2026-109618](https://insights.sbomify.com/CVE-2026-109618/): PHP Memory Corruption (critical 9.2, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3400 and fix it if it is affected.

What it is: CVE-2024-3400 is a critical command injection vulnerability in Paloaltonetworks Pan-Os, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-3400 in the wild since at least 12 Apr 2024, including in ransomware campaigns.

Affected product: Paloaltonetworks Pan-Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3400/ (Markdown: https://insights.sbomify.com/CVE-2024-3400/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3400
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3400
- OSV: https://osv.dev/vulnerability/CVE-2024-3400

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3400/
Summaries are generated and may contain mistakes; the official description above is the record.