Skip to content
Noroxi
NVD / CVE Program· CNA palo_alto

CVE-2021-3034: Cortex XSOAR: Secrets for SAML single sign-on (SSO) integration may be logged in system logs

Noroxi assessment

Priority: Monitor (action score 20/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • 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.
  • Fixed version: Palo Alto Networks Cortex XSOAR 830029, 848144, 98622.

Low priority for now. Upgrade to Palo Alto Networks Cortex XSOAR 830029, 848144, 98622 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.1 · v3.1—No exploit Fix available
Published
Mar 10, 2021
Updated
Jun 17, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-3034

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for paloaltonetworks records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
paloaltonetworkscortex 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 records

Other highest-scoring records for the same primary product.

  • CVE-2021-3044Cortex XSOAR: Unauthorized Usage of the REST API
    39Monitor
  • CVE-2021-3051Cortex XSOAR: Authentication Bypass in SAML Authentication
    32Monitor
  • CVE-2023-0003Cortex XSOAR: Local File Disclosure Vulnerability in the Cortex XSOAR Server
    26Monitor

Published before and after this one in the same product

  • Later →CVE-2021-3049Sep 8, 2021 · Cortex XSOAR: Improper Authorization of Incident Investigations Vulnerability
    17Monitor
  • Later →CVE-2022-0020Feb 10, 2022 · Cortex XSOAR: Stored Cross-Site Scripting (XSS) Vulnerability in Web Interface
    22Monitor
  • Later →CVE-2022-0027May 11, 2022 · Cortex XSOAR: Incorrect Authorization Vulnerability When Generating Reports
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Palo Alto Networks Cortex XSOAR830029Vendor (CNA)
Palo Alto Networks Cortex XSOAR848144Vendor (CNA)
Palo Alto Networks Cortex XSOAR98622Vendor (CNA)
Palo Alto Networks Cortex XSOAR98623Vendor (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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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 File

CVSS 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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records