CVE-2022-0011

PAN-OS: URL Category Exceptions Match More URLs Than Intended in URL Filtering

MEDIUM
6.5
CVSS Score
Published: February 10, 2022 at 06:10 PM UTC
Updated: June 17, 2026 at 04:19 AM UTC
2 products affected across 1 vendorPAN-OSPrisma Access

Using PAN-OS by Palo Alto Networks?

Get instant alerts when new vulnerabilities affect PAN-OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.7%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0 ≤ v < 10.0.810.0.0 ≤ v < 10.0.810.1 ≤ v < 10.1.310.1.0 ≤ v < 10.1.38.1 ≤ v < 8.1.218.1.0 ≤ v < 8.1.219.0.0 ≤ v ≤ 9.0.159.1 ≤ v < 9.1.129.1.0 ≤ v < 9.1.1210.010.18.19.0.*9.1
Affected range stops below 10.0.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.1.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.1.12, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.0 Preferred, Innovation (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_MISCMitigationVendor Advisory
https://security.paloaltonetworks.com/CVE-2022-0011

CVSS

6.5MEDIUMpalo_alto
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-436

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card