title: Cortex XDR Agent: An Uncontrolled Search Path Element Leads to Local Privilege Escalation (PE) Vulnerability
description: A local privilege escalation (PE) vulnerability exists in Palo Alto Networks Cortex XDR agent software on Windows that enables an authenticated local user with file creation privilege in the Windows root directory (such as C:\) to execute a program with elevated privileges. This issue impacts: All versions of the Cortex XDR agent when upgrading to Cortex XDR agent 7.7.0 on Windows; Cortex XDR agent 7.7.0 without content update 500 or a later version on Windows. This issue does not impact other platforms or other versions of the Cortex XDR agent.
problem types: CWE-427 Uncontrolled Search Path Element
affected:
{
platforms: Windows
product: Cortex XDR Agent
vendor: Palo Alto Networks
versions:
changes: [at: 7.7.1.62043, status: unaffected], lessThan: 7.7.1.62043 without CU-500, status: affected, version: 7.7, versionType: custom
}
{
product: Cortex XDR Agent
vendor: Palo Alto Networks
versions:
status: unaffected, version: 7.7.* with CU-500
status: unaffected, version: 7.6 all
status: unaffected, version: 7.5 CE all
status: unaffected, version: 7.4 all
status: unaffected, version: 7.5 all
status: unaffected, version: 6.1 all
status: unaffected, version: 5.0 all
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: LOCAL
availabilityImpact: HIGH
baseScore: 6.7
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: HIGH
privilegesRequired: HIGH
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
version: 3.1
]
exploits: Palo Alto Networks is not aware of any malicious exploitation of this issue.
solutions: This issue is fixed in Cortex XDR agent 7.7.0 with content update 500, Cortex XDR agent 7.7.1 build 7.7.1.62043, and all later Cortex XDR agent versions.
Ensure that Cortex XDR agent is upgraded to Cortex XDR agent 7.7.1.62043 or a later build when upgrading Cortex XDR agent to Cortex XDR agent 7.7 to prevent exposure to this vulnerability during the upgrade process.
workarounds: There are no known workarounds for this issue.