Article Number
000036156
CVE ID
000036156
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
