# CVE-2017-15944: Palo Alto Networks PAN-OS Remote Code Execution

> Remote attackers can execute arbitrary code on Palo Alto Networks PAN-OS devices via the management interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 18 Aug 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-9ppr-hv62-39w2

## What is CVE-2017-15944?

CVE-2017-15944 is a critical code injection vulnerability in Paloaltonetworks Pan-Os, published on 11 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Palo Alto Networks PAN-OS before 6.1.19, 7.0.x before 7.0.19, 7.1.x before 7.1.14, and 8.0.x before 8.0.6 allows remote attackers to execute arbitrary code via vectors involving the management interface.

Weakness: CWE-20 (Improper Input Validation), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-15944?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2017-15944?

No fix has been published for CVE-2017-15944 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 Sep 2022.

## Is CVE-2017-15944 being exploited?

Yes. Attackers have exploited CVE-2017-15944 in the wild since at least 18 Aug 2022.

Public exploit code:

- Detecion for the vulnerability CVE-2017-15944 (github_poc): https://github.com/surajraghuvanshi/PaloAltoRceDetectionAndExploit
- CVE-2017-15944 Palo Alto Networks firewalls remote root code execution POC (github_poc): https://github.com/xxnbyy/CVE-2017-15944-POC
- Palo Alto Networks readSessionVarsFromFile() Session Corruption (metasploit)
- Palo Alto Networks Firewalls - Root Remote Code Execution (exploitdb)
- Palo Alto Networks - 'readSessionVarsFromFile()' Session Corruption (Metasploit) (exploitdb)
- https://github.com/yukar1z0e/CVE-2017-15944 (github_poc): https://github.com/yukar1z0e/CVE-2017-15944

## Other vulnerabilities in Paloaltonetworks Pan-Os

- [CVE-2024-3400](https://insights.sbomify.com/CVE-2024-3400/): Palo Alto Networks PAN-OS Command Injection (critical 10.0, exploited in the wild)
- [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-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-2017-15944 and fix it if it is affected.

What it is: CVE-2017-15944 is a critical code injection vulnerability in Paloaltonetworks Pan-Os, published on 11 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-15944 in the wild since at least 18 Aug 2022.

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-2017-15944/ (Markdown: https://insights.sbomify.com/CVE-2017-15944/index.md)
```

## Sources

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

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