CVE-2024-5909

Medium
5.5
0.05.010.0
Year
2024
Published
Jun 12, 2024
Known Affected Devices
0
CVSS Score
5.5

What is CVE-2024-5909?

A problem with a protection mechanism in the Palo Alto Networks Cortex XDR agent on Windows devices allows a low privileged local Windows user to disable the agent. This issue may be leveraged by malware to disable the Cortex XDR agent and then to perform malicious activity.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
AV
Attack Vector
Local

Requires local access — attacker must be logged in or have physical access to the device.

AC
Attack Complexity
Low

No special conditions required. Exploit can be performed reliably and repeatedly.

PR
Privileges Required
Low

Basic user account required (e.g. standard login without admin rights).

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
None

No confidentiality impact. Sensitive data is not exposed.

I
Integrity Impact
None

No integrity impact. Data cannot be modified.

A
Availability Impact
High

Complete denial of service. The component becomes fully unavailable.

Known Affected Devices

FAQ

How severe is CVE-2024-5909?

CVE-2024-5909 has a CVSS score of 5.5/10, rated as Medium. Review the affected products list and apply vendor patches.

What does the CVSS score mean for CVE-2024-5909?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2024-5909 scores 5.5/10 (Medium). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2024-5909?

The list of devices confirmed to be affected by CVE-2024-5909 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2024-5909?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.