# CVE-2019-1575: Information disclosure in Palo Alto Networks PAN-OS

> Authenticated read-only users can extract API keys and credentials from the XML API, potentially leading to privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mxj5-9849-29f5

## What is CVE-2019-1575?

CVE-2019-1575 is a high-severity vulnerability in Paloaltonetworks Pan-Os, published on 16 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Information disclosure in PAN-OS 7.1.23 and earlier, PAN-OS 8.0.18 and earlier, PAN-OS 8.1.8-h4 and earlier, and PAN-OS 9.0.2 and earlier may allow for an authenticated user with read-only privileges to extract the API key of the device and/or the username/password from the XML API (in PAN-OS) and possibly escalate privileges granted to them.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-1575?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2019-1575?

No fix has been published for CVE-2019-1575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-1575 being exploited?

There is no known exploitation of CVE-2019-1575 in the wild and no public exploit code.

## 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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1575 and fix it if it is affected.

What it is: CVE-2019-1575 is a high-severity vulnerability in Paloaltonetworks Pan-Os, published on 16 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1575 in the wild and no public exploit code.

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

## Sources

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

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