Security Advisory Articles

Report Inappropriate Content

Article Number

000036156

CVE ID

CVE-2017-11427, CVE-2017-11428, CVE-2017-11429, CVE-2017-11430, CVE-2018-0489, CVE-2018-7340

Applies To

RSA Product Set: All RSA Products that support SAML

Article Summary

Researchers have identified and reported a vulnerability (on February 27, 2018) that may affect certain Service Provider (“SP”) implementations of SAML-based single-sign-on (“SSO”) systems. SAML libraries, affected by this vulnerability, may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.

Resolution

RSA has investigated this issue to identify any potential impact to RSA software and cloud based services (“RSA products”) and will update this article with any new information as it becomes available, including impacted RSA products and remediation steps. Only the RSA products that support SAML-based SSO are listed here. RSA products that do not support SAML are not impacted by these vulnerabilities and are not listed in this article.

RSA Product Name	Versions	Impacted?	Details	Last Updated
Access Manager	6.2.x	Not Impacted	Access Manager supports SAML as an Identity Provider (IDP) and therefore is not impacted by the vulnerability. To prevent attackers from attempting or exploiting the vulnerability in your applications that may talk to a vulnerable third-party SP implementation, RSA recommends that you: 1. Ensure that accounts in your identity source can only be created by authorized individuals and, especially if any self-service account provisioning is offered, that account names adhere to specific guidelines to reduce the opportunity for exploitation. 2. Reach out to your SP application providers and make sure they use non-vulnerable SAML products or libraries, or confirm they are using the latest versions that have been patched to address the vulnerability.	2018-03-15
Adaptive Authentication Cloud		Not Impacted	The SAML implementation used is not affected by the vulnerability.	2018-03-15
Archer Hosted	All Supported	Not Impacted	SAML responses and claims are handled by Microsoft ADFS which is not affected by the vulnerability.	2018-03-15
Archer Platform	All Supported	Not Impacted	SAML responses and claims are handled by Microsoft ADFS which is not affected by the vulnerability.	2018-03-15
Archer Security Operations Management (SecOps)	All Supported	Not Impacted	SAML responses and claims are handled by Microsoft ADFS which is not affected by the vulnerability.	2018-03-15
Archer Vulnerability & Risk Manager (VRM)	All Supported	Not Impacted	SAML responses and claims are handled by Microsoft ADFS which is not affected by the vulnerability.	2018-03-15
Federated Identity Manager (FIM)	All Supported	Not Impacted	FIM is not impacted by the vulnerability. FIM has signature verification procedure wherein any signed SAML response/assertion if modified (e.g., injection of any comments as stated in reported SAML vulnerability definition) would result in signature verification failure. RSA recommends that customers follow the product documentation to use signing and/or encryption for SAML messages.	2018-03-15
Identity Governance & Lifecycle, Via Lifecycle & Governance, Identity Management & Governance	7.1, 7.0.2, 7.0.1, 7.0, 6.9.x	Not Impacted	Product uses libraries which are not affected by the vulnerability.	2018-03-15
SecurID Access Cloud Service	All Supported	Not Impacted	SecurID Access Cloud Service supports SAML as an Identity Provider (IDP) and therefore is not impacted by the vulnerability. To prevent attackers from attempting or exploiting the vulnerability in your applications that may talk to a vulnerable third-party SP implementation, RSA recommends that you: 1. Ensure that accounts in your identity source can only be created by authorized individuals and, especially if any self-service account provisioning is offered, that account names adhere to specific guidelines to reduce the opportunity for exploitation. 2. Reach out to your SP application providers and make sure they use non-vulnerable SAML products or libraries, or confirm they are using the latest versions that have been patched to address the vulnerability.	2018-03-15
SecurID Access IDR VM	All Supported	Not Impacted	SecurID Access IDR VM supports SAML as an Identity Provider (IDP) and as a Service Provider (SP). SecurID Access uses a SAML implementation that is not affected by the vulnerability. To prevent attackers from attempting or exploiting the vulnerability in your applications that may talk to a vulnerable third-party SP implementation, RSA recommends that you: 1. Ensure that accounts in your identity source can only be created by authorized individuals and, especially if any self-service account provisioning is offered, that account names adhere to specific guidelines to reduce the opportunity for exploitation. 2. Reach out to your SP application providers and make sure they use non-vulnerable SAML products or libraries, or confirm they are using the latest versions that have been patched to address the vulnerability.	2018-03-15

Notes

References:

CERT/CC Vulnerability Note: https://www.kb.cert.org/vuls/id/475445
Researcher’s (Duo Labs) blog post: https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations

Disclaimer

Read and use the information in this RSA Security Advisory to assist in avoiding any situation that might arise from the problems described herein. If you have any questions regarding this product alert, contact RSA Software Technical Support at 1- 800 995 5095. RSA Security LLC and its affiliates, including without limitation, its ultimate parent company, Dell EMC, distributes RSA Security Advisories in order to bring to the attention of users of the affected RSA products, important security information. RSA recommends that all users determine the applicability of this information to their individual situations and take appropriate action. The information set forth herein is provided 'as is' without warranty of any kind. RSA disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event, shall RSA, its affiliates or suppliers, be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if RSA, its affiliates or suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply.