Cortex Xdr AgentApplication · Paloaltonetworks
CVE-2023-0002
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 local user to execute privileged cytool commands that disable or uninstall the agent.
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 flaw in its protection mechanism that allows a local authenticated user to bypass restrictions and execute privileged cytool commands with elevated privileges. This enables the user to disable or uninstall the security agent, effectively neutralizing endpoint protection.
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
>= 5.0, < 5.0.12.22203>= 7.5, <= 7.5.101CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm Cortex XDR Agent is installedCheck for the presence of Cortex XDR agent on Windows by looking in Programs and Features for 'Palo Alto Networks Cortex XDR' or by checking the Windows services for the 'Cortex XDR' serviceAffected if Cortex XDR Agent is not found on the system, this CVE does not apply
-
Determine installed Cortex XDR versionRun 'cytool.exe version' from the Cortex XDR installation directory (typically C:\Program Files\Palo Alto Networks\Cortex XDR\) or check the version in Programs and FeaturesAffected if Installed version falls within >= 5.0 and < 5.0.12.22203 OR >= 7.5 and <= 7.5.101, the system is potentially affected
-
Verify cytool.exe existsConfirm cytool.exe is present in the Cortex XDR installation directoryAffected if cytool.exe is present and the version is in the affected range, the system is potentially affected
-
Test if unprivileged users can execute privileged cytool commandsAs a non-administrator user, attempt to run cytool.exe with elevated commands such as 'cytool.exe disable' or 'cytool.exe help' to verify if the protection mechanism can be bypassedAffected if An unprivileged authenticated user can execute privileged cytool commands or bypass the protection mechanism, the system is affected by this CVE
A system is affected if Cortex XDR Agent is installed with a version in the ranges 5.0 to 5.0.12.22203 (exclusive of 5.0.12.22203) or 7.5 to 7.5.101 (inclusive), and unprivileged users can execute privileged cytool commands.
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 · scoped5.0.12.22203
Apply the vendor-supplied patch for CVE-2023-0002 to the Cortex XDR agent on all affected Windows systems. Verify that the protection mechanism properly restricts cytool command execution to authorized administrators only.
Cortex XDR Agent 5.0.12.22203 or later (5.x branch); Cortex XDR Agent version > 7.5.101 (7.5.x branch)
- 1. Identify the currently installed Cortex XDR agent version on affected Windows devices using the cytool version command or the Cortex XDR console
- 2. For devices running Cortex XDR agent version 5.0.x (< 5.0.12.22203): Upgrade to version 5.0.12.22203 or later
- 3. For devices running Cortex XDR agent version 7.5.x (7.5 through 7.5.101): Upgrade to a version beyond 7.5.101 (check Palo Alto Networks support for the latest stable 7.5.x release)
- 4. Verify the upgrade was successful by running cytool version and confirming the new version number
- 5. Test that the protection mechanism is working by attempting to run privileged cytool commands as a non-admin user (these should now be blocked)
- 6. Document the upgrade in change management systems
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cortex Xdr Agent
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.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 $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0002 — 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-2023-0002 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