Cortex Xdr AgentApplication · Paloaltonetworks
CVE-2024-9469
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA problem with a detection mechanism in the Palo Alto Networks Cortex XDR agent on Windows devices enables a user with Windows non-administrative privileges to disable the agent. This issue may be leveraged by malware to disable the Cortex XDR agent and then to perform malicious activity.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Cortex XDR agent on Windows has a flawed detection mechanism that allows non-administrative users to disable the security agent. This vulnerability can be exploited by malware to bypass security controls by stopping the XDR protection before executing malicious payloads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Cortex Xdr AgentApplication
>= 7.9, < 7.9.102= 8.3.0= 8.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Cortex XDR Agent versionOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\PaloAltoNetworks\Cortex\XDR\Agent or check Programs and Features for the installed versionAffected if The installed version falls within >= 7.9, < 7.9.102, = 8.3.0, or = 8.4.0
-
Verify Cortex XDR service configurationOpen Services console (services.msc), locate the Cortex XDR service, right-click and select Properties, then check the Log On tabAffected if The service is configured to run under a non-administrative account or if the service allows stop/pause by non-admin users via Service Control Manager permissions
-
Review Windows Security event logs for service manipulationOpen Event Viewer, navigate to Windows Logs > Security, and filter for Event ID 7036 (Service Control Manager) or search for 'Cortex' or 'XDR' in task category for service stop eventsAffected if Event logs show successful service stop operations performed by non-administrative users
-
Check for unauthorized attempts to disable protectionUse PowerShell to query recent Security event logs: Get-WinEvent -FilterHashtable @{LogName='Security';ID=7036} -MaxEvents 100 | Where-Object {$_.Message -like '*Cortex*' -or $_.Message -like '*XDR*'}Affected if Any service stop events involving Cortex XDR are present in the logs from non-admin accounts
Your environment is affected if the Cortex XDR Agent version is 7.9 through 7.9.101, exactly 8.3.0, or exactly 8.4.0 and non-administrative users have been able to stop the service.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.9.102
Apply the vendor-supplied patch from Palo Alto Networks. Until the patch is deployed, monitor for attempts to disable the Cortex XDR service using Windows event logs and endpoint detection tools.
Cortex XDR Agent 7.9.102 or later (for 7.9.x branch); upgrade to latest available version for 8.3.x and 8.4.x branches
- Identify the currently installed Cortex XDR Agent version on Windows devices
- For version 7.9.x: Upgrade to version 7.9.102 or later
- For version 8.3.0: Upgrade to the next available patch that addresses this vulnerability
- For version 8.4.0: Upgrade to the next available patch that addresses this vulnerability
- Verify the upgrade was successful by checking the agent version and ensuring it remains running
- Confirm the detection mechanism is functioning properly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cortex Xdr Agent
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9469 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data