Cortex Xdr AgentApplication · Paloaltonetworks
CVE-2024-5909
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 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.
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 confidenceA vulnerability in the protection mechanism of Palo Alto Networks Cortex XDR agent on Windows allows a low-privileged local Windows user to disable the security agent, potentially enabling malware to bypass endpoint protection controls.
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.1, < 8.1.2>= 8.2, < 8.2.1CVSS 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.
-
Verify Cortex XDR agent is installedCheck Windows registry key HKLM\SOFTWARE\PaloAltoNetworks\Cortex\XDR\InstallPath, or look for the service named 'Cyvera' or 'Cortex XDR' in services.msc, or check Program Files for Cortex XDR installation folderAffected if Cortex XDR agent is not found on the system
-
Retrieve installed Cortex XDR versionQuery the Windows registry at HKLM\SOFTWARE\PaloAltoNetworks\Cortex\XDR\Version or right-click the executable in the installation folder and view Properties > Details for the FileVersionAffected if Unable to determine the version from registry or executable properties
-
Compare version against affected rangesIf version is 7.9.x, ensure x is >= 102; if 8.1.x, ensure x >= 2; if 8.2.x, ensure x >= 1; versions below these thresholds are affectedAffected if Installed version falls in ranges: 7.9.0 to 7.9.101, 8.1.0 to 8.1.1, or 8.2.0
-
Confirm agent protection is activeOpen Cortex XDR console or run 'CyveraConsole.exe status' from the installation folder to verify the protection module is enabled and running, or check that the Cyvera service status is RunningAffected if Agent protection shows as disabled or the service is not running (though this alone does not confirm the vulnerability is exploitable, it indicates potential tampering)
The system is affected if Cortex XDR agent is installed with version 7.9.x below 102, 8.1.x below 2, or 8.2.x below 1, and the protection mechanism can potentially be disabled by a low-privileged user.
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.1028.1.28.2.1
Apply vendor-supplied patches for Cortex XDR agent when available; monitor for attempts to disable the agent; implement additional detection controls for endpoint protection tampering.
7.9.102, 8.1.2, or 8.2.1 (depending on current branch)
- Upgrade Cortex XDR Agent to version 7.9.102 or later if running 7.9.x
- OR upgrade to version 8.1.2 or later if running 8.1.x
- OR upgrade to version 8.2.1 or later if running 8.2.x
- Verify the upgrade was successful by confirming the Cortex XDR agent is running and cannot be disabled by low-privileged users
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
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5909 — 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-5909 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