Cortex XsoarApplication · Paloaltonetworks
CVE-2023-0003
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 file disclosure vulnerability in the Palo Alto Networks Cortex XSOAR server software enables an authenticated user with access to the web interface to read local files from the server.
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 file disclosure vulnerability in Palo Alto Networks Cortex XSOAR allows authenticated users with web interface access to read arbitrary local files from the server. The vulnerability likely involves improper path validation or traversal in file read functionality accessible through the web application.
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 XsoarApplication
>= 6.10.0, < 6.10.0.185964= 6.6.0= 6.8.0= 6.9.0
FedoraOperating system
= 37= 38= 39CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify installed Cortex XSOAR versionAccess the Cortex XSOAR web interface and navigate to Settings > About, or run the command `sudo docker images | grep demisto` to list the installed Docker images and their tags.Affected if The version displayed matches any of these: 6.6.0, 6.8.0, 6.9.0, or a version >= 6.10.0 but < 6.10.0.185964.
-
Confirm web interface is accessibleVerify that the Cortex XSOAR web UI is reachable by attempting to access the login page at the configured hostname or IP address over HTTPS/HTTP.Affected if The web interface responds and accepts authentication requests.
-
Verify authenticated user access existsReview the Users and Roles configuration under Settings > Users > Users to confirm there are active user accounts with web interface access privileges.Affected if Any user account with access to the web interface exists in the system.
-
Check for path traversal indicators in audit logsReview Cortex XSOAR audit logs (Settings > Audit > Audit) or system logs for suspicious file access patterns, particularly entries containing '../' or absolute file paths in file read operations.Affected if Unusual file access requests appear in logs, especially from authenticated users accessing system files outside expected directories.
A user is affected if their Cortex XSOAR version falls within 6.6.0, 6.8.0, 6.9.0, or >= 6.10.0 but < 6.10.0.185964 AND the web interface is accessible to authenticated users.
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.
From vendor data6.10.0.185964
Restrict and audit web interface access to trusted users only, apply available vendor patches, and implement least-privilege access controls for the Cortex XSOAR platform.
Fix this in Cortex Xsoar
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0003 — 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-0003 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