# CVE-2025-0123: PAN-OS: Information Disclosure Vulnerability in HTTP/2 Packet Captures

> Unlicensed administrators can view clear-text HTTP/2 data in packet captures, exposing sensitive information to those with management access.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/AU:N/R:A/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-379r-vg26-3rr8

## What is CVE-2025-0123?

CVE-2025-0123 is a medium-severity vulnerability in Palo Alto Networks Cloud NGFW, published on 11 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Palo Alto Networks PAN-OS® software enables unlicensed administrators to view clear-text data captured using the  packet capture feature https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-admin/monitoring/take-packet-captures/take-a-custom-packet-capture  in decrypted HTTP/2 data streams traversing network interfaces on the firewall. HTTP/1.1 data streams are not impacted.

In normal conditions, decrypted packet captures are available to firewall administrators after they obtain and install a free Decryption Port Mirror license. The license requirement ensures that this feature can only be used after approved personnel purposefully activate the license. For more information, review how to  configure decryption port mirroring https://docs.paloaltonetworks.com/network-security/decryption/administration/monitoring-decryption/configure-decryption-port-mirroring .

The administrator must obtain network access to the management interface (web, SSH, console, or telnet) and successfully authenticate to exploit this issue. Risk of this issue can be greatly reduced by restricting access to the management interface to only trusted administrators and from only internal IP addresses according to our recommended  critical deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 .

Customer firewall administrators do not have access to the packet capture feature in Cloud NGFW. This feature is available only to authorized Palo Alto Networks personnel permitted to perform troubleshooting.

Prisma® Access is not impacted by this vulnerability.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-0123?


## How do I fix CVE-2025-0123?

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

## Is CVE-2025-0123 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0123 and fix it if it is affected.

What it is: CVE-2025-0123 is a medium-severity vulnerability in Palo Alto Networks Cloud NGFW, published on 11 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0123 in the wild and no public exploit code.

Affected product: Palo Alto Networks Cloud NGFW. 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-2025-0123/ (Markdown: https://insights.sbomify.com/CVE-2025-0123/index.md)
```

## Sources

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

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