Cortex XSOAR: Secrets for SAML single sign-on (SSO) integration may be logged in system logs
An information exposure through log file vulnerability exists in Cortex XSOAR software where the secrets configured for the SAML single sign-on (SSO) integration can be logged to the '/var/log/demisto/' server logs when testing the integration during setup. This logged information includes the private key and identity provider certificate used to configure the SAML SSO integration. This issue impacts: Cortex XSOAR 5.5.0 builds earlier than 98622; Cortex XSOAR 6.0.1 builds earlier than 830029; Cortex XSOAR 6.0.2 builds earlier than 98623; Cortex XSOAR 6.1.0 builds earlier than 848144.
- Published
- Mar 10, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- CWE-532
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · palo_alto
- 5.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| paloaltonetworks | cortex xsoar | cpe:2.3:a:paloaltonetworks:cortex_xsoar |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- paloaltonetworks cortex xsoar5.5.0
- paloaltonetworks cortex xsoar6.0.1
- paloaltonetworks cortex xsoar6.0.2
- paloaltonetworks cortex xsoar6.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (palo_alto). Independent of NVD's CPE analysis and usually ahead of it.
Palo Alto Networks Cortex XSOAR
- 5.5.0 and later · before 98622affectedfixed in 98622
- 6.0.2 and later · before 98623affectedfixed in 98623
- 6.0.1 and later · before 830029affectedfixed in 830029
- 6.1.0 and later · before 848144affectedfixed in 848144
Same product
paloaltonetworks: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3044Cortex XSOAR: Unauthorized Usage of the REST API39Monitor
- CVE-2021-3051Cortex XSOAR: Authentication Bypass in SAML Authentication32Monitor
- CVE-2023-0003Cortex XSOAR: Local File Disclosure Vulnerability in the Cortex XSOAR Server26Monitor
- CVE-2022-0020Cortex XSOAR: Stored Cross-Site Scripting (XSS) Vulnerability in Web Interface22Monitor
- CVE-2022-0027Cortex XSOAR: Incorrect Authorization Vulnerability When Generating Reports17Monitor
- CVE-2021-3049Cortex XSOAR: Improper Authorization of Incident Investigations Vulnerability17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Palo Alto Networks Cortex XSOAR | 830029 | Vendor (CNA) |
| Palo Alto Networks Cortex XSOAR | 848144 | Vendor (CNA) |
| Palo Alto Networks Cortex XSOAR | 98622 | Vendor (CNA) |
| Palo Alto Networks Cortex XSOAR | 98623 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.