# CVE-2022-0028: Palo Alto Networks PAN-OS Reflected Amplification Denial-of-Service

> Misconfigured URL filtering allows attackers to launch reflected DoS attacks, implicating the firewall as the source.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Yes, since 22 Aug 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-r3j6-h9rm-9q33

## What is CVE-2022-0028?

CVE-2022-0028 is a high-severity denial of service vulnerability in Paloaltonetworks Pan-Os, published on 10 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A PAN-OS URL filtering policy misconfiguration could allow a network-based attacker to conduct reflected and amplified TCP denial-of-service (RDoS) attacks. The DoS attack would appear to originate from a Palo Alto Networks PA-Series (hardware), VM-Series (virtual) and CN-Series (container) firewall against an attacker-specified target. To be misused by an external attacker, the firewall configuration must have a URL filtering profile with one or more blocked categories assigned to a source zone that has an external facing interface. This configuration is not typical for URL filtering and, if set, is likely unintended by the administrator. If exploited, this issue would not impact the confidentiality, integrity, or availability of our products. However, the resulting denial-of-service (DoS) attack may help obfuscate the identity of the attacker and implicate the firewall as the source of the attack. We have taken prompt action to address this issue in our PAN-OS software. All software updates for this issue are expected to be released no later than the week of August 15, 2022. This issue does not impact Panorama M-Series or Panorama virtual appliances. This issue has been resolved for all Cloud NGFW and Prisma Access customers and no additional action is required from them.

Weakness: CWE-406 (Insufficient Control of Network Message Volume (Network Amplification))

## Which versions are affected by CVE-2022-0028?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2022-0028?

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

## Is CVE-2022-0028 being exploited?

Yes. Attackers have exploited CVE-2022-0028 in the wild since at least 22 Aug 2022.

## 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-2022-0028 and fix it if it is affected.

What it is: CVE-2022-0028 is a high-severity denial of service vulnerability in Paloaltonetworks Pan-Os, published on 10 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-0028 in the wild since at least 22 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-2022-0028/ (Markdown: https://insights.sbomify.com/CVE-2022-0028/index.md)
```

## Sources

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

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