CVE-2024-5905

4.4 MEDIUM

📋 TL;DR

A local privilege bypass vulnerability in Palo Alto Networks Cortex XDR agent on Windows allows low-privileged users to disrupt some agent functionality. This affects Windows devices running vulnerable versions of the Cortex XDR agent. The vulnerability does not allow disruption of core protection mechanisms.

💻 Affected Systems

Products:
  • Palo Alto Networks Cortex XDR agent
Versions: Specific versions not specified in CVE description; check vendor advisory for exact affected versions
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects Windows installations of Cortex XDR agent. Requires local user access to the system.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Local low-privileged user could temporarily disable some Cortex XDR agent monitoring or reporting functions, potentially creating a window for other attacks.

🟠

Likely Case

Local user could cause service disruption or disable specific agent features, but core security protections remain intact.

🟢

If Mitigated

With proper access controls and monitoring, impact is limited to temporary service disruption with no compromise of security functions.

🌐 Internet-Facing: LOW - This is a local privilege issue requiring authenticated access to the Windows system.
🏢 Internal Only: MEDIUM - Internal users with local access to Windows workstations could exploit this to disrupt endpoint security monitoring.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires local access to Windows system with low privileges. No public exploit code mentioned in CVE.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific fixed versions

Vendor Advisory: https://security.paloaltonetworks.com/CVE-2024-5905

Restart Required: Yes

Instructions:

1. Check vendor advisory for affected versions. 2. Update Cortex XDR agent to latest version. 3. Restart affected Windows systems. 4. Verify agent functionality post-update.

🔧 Temporary Workarounds

Restrict local user privileges

windows

Limit local user account privileges on Windows systems to reduce attack surface

Implement least privilege principle for local accounts
Use Group Policy to restrict user permissions

Monitor agent service status

windows

Implement monitoring for Cortex XDR agent service disruptions

Set up alerts for agent service state changes
Monitor Windows Event Logs for service interruptions

🧯 If You Can't Patch

  • Implement strict access controls to limit local user privileges on Windows systems
  • Monitor for unusual agent service disruptions and investigate any unauthorized attempts to modify agent functionality

🔍 How to Verify

Check if Vulnerable:

Check Cortex XDR agent version against vendor advisory for affected versions

Check Version:

Check agent version through Cortex XDR console or agent interface

Verify Fix Applied:

Verify agent version is updated to patched version and agent functionality is normal

📡 Detection & Monitoring

Log Indicators:

  • Unexpected agent service restarts
  • Unauthorized attempts to modify agent processes or services
  • Security agent functionality alerts

Network Indicators:

  • Unusual agent communication patterns
  • Missing expected agent heartbeat signals

SIEM Query:

Search for Windows Event IDs related to service control (7036, 7034) for Cortex XDR agent service

🔗 References

📤 Share & Export