# CVE-2022-0011: PAN-OS: URL Category Exceptions Match More URLs Than Intended in URL Filtering

> Improper URL matching in PAN-OS allows attackers to bypass URL filtering policies if administrators use specific wildcard patterns in exception lists.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 10 Feb 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pc4w-x9p8-64j7

## What is CVE-2022-0011?

CVE-2022-0011 is a medium-severity vulnerability in Paloaltonetworks Pan-Os, published on 10 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PAN-OS software provides options to exclude specific websites from URL category enforcement and those websites are blocked or allowed (depending on your rules) regardless of their associated URL category. This is done by creating a custom URL category list or by using an external dynamic list (EDL) in a URL Filtering profile. When the entries in these lists have a hostname pattern that does not end with a forward slash (/) or a hostname pattern that ends with an asterisk (*), any URL that starts with the specified pattern is considered a match. Entries with a caret (^) at the end of a hostname pattern match any top level domain. This may inadvertently allow or block more URLs than intended and allowing more URLs than intended represents a security risk. For example: example.com will match example.com.website.test example.com.* will match example.com.website.test example.com.^ will match example.com.test You should take special care when using such entries in policy rules that allow traffic. Where possible, use the exact list of hostname names ending with a forward slash (/) instead of using wildcards. PAN-OS 10.1 versions earlier than PAN-OS 10.1.3; PAN-OS 10.0 versions earlier than PAN-OS 10.0.8; PAN-OS 9.1 versions earlier than PAN-OS 9.1.12; all PAN-OS 9.0 versions; PAN-OS 8.1 versions earlier than PAN-OS 8.1.21, and Prisma Access 2.2 and 2.1 versions do not allow customers to change this behavior without changing the URL category list or EDL.

Weakness: CWE-436 (Interpretation Conflict)

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

It affects 2 products.


Products: Paloaltonetworks Pan-Os, Paloaltonetworks Prisma Access.

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

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

## Is CVE-2022-0011 being exploited?

There is no known exploitation of CVE-2022-0011 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-2022-0011 and fix it if it is affected.

What it is: CVE-2022-0011 is a medium-severity vulnerability in Paloaltonetworks Pan-Os, published on 10 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0011 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-2022-0011/ (Markdown: https://insights.sbomify.com/CVE-2022-0011/index.md)
```

## Sources

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

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