Hash: SHA256

             AUSCERT External Security Bulletin Redistribution

                  Cortex XSOAR: Multiple Vulnerabilities
                             14 September 2021


        AusCERT Security Bulletin Summary

Product:           Cortex XSOAR
Publisher:         Palo Alto
Operating System:  Network Appliance
Impact/Access:     Access Confidential Data -- Remote/Unauthenticated
                   Unauthorised Access      -- Remote/Unauthenticated
                   Reduced Security         -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2021-3051 CVE-2021-3049 

Original Bulletin: 

Revision History:  September 14 2021: Vendor removed unsupported Cortex XSOAR versions from solution
                   September  9 2021: Initial Release

- --------------------------BEGIN INCLUDED TEXT--------------------

Palo Alto Networks Security Advisories / CVE-2021-3051

CVE-2021-3051 Cortex XSOAR: Authentication Bypass in SAML Authentication

Severity 8.1 . HIGH
Attack Vector NETWORK
Attack Complexity HIGH
Privileges Required NONE
User Interaction NONE
Confidentiality Impact HIGH
Integrity Impact HIGH
Availability Impact HIGH
Published 2021-09-08
Updated 2021-09-13
Discovered externally


An improper verification of cryptographic signature vulnerability exists in
Cortex XSOAR SAML authentication that enables an unauthenticated network-based
attacker with specific knowledge of the Cortex XSOAR instance to access
protected resources and perform unauthorized actions on the Cortex XSOAR

This issue impacts:

Cortex XSOAR 5.5.0 builds earlier than 1578677;

Cortex XSOAR 6.1.0 builds earlier than 1578663;

Cortex XSOAR 6.2.0 builds earlier than 1578666.

All Cortex XSOAR instances hosted by Palo Alto Networks are protected from this
vulnerability; no additional action is required for these instances.

Product Status

     Versions      Affected  Unaffected
Cortex XSOAR 6.2.0 < 1578666 >= 1578666
Cortex XSOAR 6.1.0 < 1578663 >= 1578663
Cortex XSOAR 5.5.0 < 1578677 >= 1578677

Required Configuration for Exposure

This issue is applicable only to Cortex XSOAR configurations with SAML
authentication integration enabled.

You can determine if your configuration has SAML authentication integration
enabled by selecting 'Settings > Servers & Services' and searching for 'SAML'.

Severity: HIGH

CVSSv3.1 Base Score: 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)

Exploitation Status

Palo Alto Networks is not aware of any malicious attempts to exploit this

Weakness Type

CWE-347 Improper Verification of Cryptographic Signature


This issue is fixed in Cortex XSOAR 5.5.0 build 1578677, Cortex XSOAR 6.1.0
build 1578663, Cortex XSOAR 6.2.0 build 1578666, and all later Cortex XSOAR

Workarounds and Mitigations

To completely prevent this issue from being exploited before you can upgrade
your Cortex XSOAR server, disable SAML authentication integration.

You can also restrict network access to the Cortex XSOAR server to allow only
trusted users to further reduce the impact of this issue.


This issue was found by a customer of Palo Alto Networks during a security

Frequently Asked Questions

Q. Are there any indicators of compromise or breach related to this

    Cortex XSOAR Audit Trail will list all performed administrative actions.
    The presence of unexpected actions, new integrations, or additional users
    sometimes indicates a breach. To view an audit trail, select 'Settings >
    Users and Roles > Audit Trail' from the web client.

Q. Is this issue a remote code execution (RCE) vulnerability?

    This issue is not a remote code execution (RCE) vulnerability. This issue
    enables an unauthorized attacker with specific knowledge of the instance to
    perform actions on behalf of a Cortex XSOAR administrator.

Q. Has this issue been exploited in the wild?

    No evidence of active exploitation was identified at the time this advisory
    was published.

Q. What logs should I examine for clues of a compromise?

    You can examine the Cortex XSOAR Audit Trail and the application server log
    (/var/log/demisto/server.log) for clues that indicate a compromise.

    The presence of new or unexpected users and API keys might indicate a


2021-09-13 Removed unsupported Cortex XSOAR versions from solution
2021-09-08 Initial publication
Terms of usePrivacyProduct Security Assurance and Vulnerability Disclosure
Policy Report vulnerabilitiesManage subscriptions
(C) 2020 Palo Alto Networks, Inc. All rights reserved.

- -------------------------------------------------------------------------------

Palo Alto Networks Security Advisories / CVE-2021-3049

CVE-2021-3049 Cortex XSOAR: Improper Authorization of Incident Investigations

Severity 2.6 . LOW
Attack Vector NETWORK
Attack Complexity HIGH
Privileges Required LOW
User Interaction REQUIRED
Confidentiality Impact LOW
Integrity Impact NONE
Availability Impact NONE
Published 2021-09-08
Updated 2021-09-08
Discovered externally


An improper authorization vulnerability in the Palo Alto Networks Cortex XSOAR
server enables an authenticated network-based attacker with investigation read
permissions to download files from incident investigations of which they are
aware but are not a part of.

This issue impacts:

All Cortex XSOAR 5.5.0 builds;

Cortex XSOAR 6.1.0 builds earlier than 12099345.

This issue does not impact Cortex XSOAR 6.2.0 versions.

Product Status

     Versions       Affected  Unaffected
Cortex XSOAR 6.2.0 None       all
Cortex XSOAR 6.1.0 < 12099345 >= 12099345
Cortex XSOAR 5.5.0 all

Severity: LOW

CVSSv3.1 Base Score: 2.6 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N)

Exploitation Status

Palo Alto Networks is not aware of any malicious exploitation of this issue.

Weakness Type

CWE-285 Improper Authorization


This issue is fixed in Cortex XSOAR 6.1.0 build 12099345 and all later Cortex
XSOAR versions.

There are currently no Cortex XSOAR 5.5.0 updates available for this issue.

Workarounds and Mitigations

There are no known workarounds for this issue.


Palo Alto Networks would like to thank CAGIP for discovering and reporting this


2021-09-08 Initial publication

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:


Australian Computer Emergency Response Team
The University of Queensland
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
Comment: http://www.auscert.org.au/render.html?it=1967