ESA-2014-160: RSA® Adaptive Authentication (On-Premise) Authentication Bypass Vulnerability

[Security Alert <Security_Alert@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ESA-2014-160: RSA® Adaptive Authentication (On-Premise) Authentication Bypass 
Vulnerability

EMC Identifier: ESA-2014-160

CVE Identifier: CVE-2014-4631

Severity Rating: CVSS: 6.8 (AV:N/AC:M/Au:N/C:P/I:P/A:P)
 
Affected Products:

RSA Adaptive Authentication (On-Premise) 6.0.2.1 to 7.1 P3 (inclusive)
RSA Adaptive Authentication Integration Adapters 1.x and 2.x
 
Unaffected Products:

RSA Adaptive Authentication (Hosted) all versions

Summary: 

RSA Adaptive Authentication (On-Premise) 6.0.2.1 to 7.1 P3 (inclusive) are 
potentially vulnerable to an authentication bypass vulnerability, if a device 
binding request is sent in an AAOP challenge SOAP call.
 
Details:

When requesting device binding in a Challenge SOAP call, permanent device 
binding takes place regardless of the success or failure of the authentication. 
This could potentially lead to an authentication bypass scenario.
 
In RSA Adaptive Authentication Integration Adapters, a device binding request 
is sent in the Challenge SOAP call for Out-of-Band Phone (Authentify) 
functionality only.
 
Recommendation:

RSA Adaptive Authentication customers who submit device binding request within 
a Challenge call or are using the RSA Adaptive Authentication Integration 
Adapters with Out-of-Band Phone (Authentify) functionality are recommended to 
upgrade to RSA Adaptive Authentication On-Premise 7.1 P4, which contain fixes 
to resolve this issue.
 
In order to determine if their Adaptive Authentication deployment is vulnerable 
to this issue, customers need to identify if Integration Adapters are used with 
Out-of-Band Phone (Authentify) functionality or, if using the API directly, 
need to review their implementation to determine if device binding is requested 
as part of the Challenge SOAP call.
 
For any customers impacted by this implementation issue, RSA recommends 
upgrading to RSA Adaptive Authentication On-Premise 7.1 P4 in which permanent 
device binding is not established unless successful authentication occurs in an 
Authentication or a QueryAuthStatus SOAP call.
 
Integration Adapter customers must upgrade their Adaptive Authentication 
installation to RSA Adaptive Authentication On-Premise 7.1 P4 to resolve this 
issue. Adaptive Authentication customers who are unable to upgrade to RSA AAOP 
7.1 P4, but have determined they are vulnerable to this issue, may 
alternatively alter their API usage by moving the DeviceManagementRequest from 
the Challenge to the Authenticate or QueryAuthStatus call, depending on 
Challenge mechanism used, which will also ensure the device binding only occurs 
upon successful authentication.
 

Obtaining Documentation:
To obtain RSA documentation, log on to RSA SecurCare Online at 
https://knowledge.rsasecurity.com and click Products in the top navigation 
menu. Select the specific product whose documentation you want to obtain. 
Scroll to the section for the product version that you want and click the set 
link.

Severity Rating:
For an explanation of Severity Ratings, refer to the Knowledge Base Article, 
?Security Advisories Severity Rating? at 
https://knowledge.rsasecurity.com/scolcms/knowledge.aspx?solution=a46604. RSA 
recommends all customers take into account both the base score and any relevant 
temporal and environmental scores which may impact the potential severity 
associated with particular security vulnerability.

Obtaining More Information:
For more information about RSA products, visit the RSA web site at 
http://www.rsa.com.

Getting Support and Service:
For customers with current maintenance contracts, contact your local RSA 
Customer Support center with any additional questions regarding this RSA 
SecurCare Note. For contact telephone numbers or e-mail addresses, log on to 
RSA SecurCare Online at https://knowledge.rsasecurity.com, click Help & 
Contact, and then click the Contact Us - Phone tab or the Contact Us - Email 
tab.

General Customer Support Information:
http://www.emc.com/support/rsa/index.htm

RSA SecurCare Online:
https://knowledge.rsasecurity.com

EOPS Policy:
RSA has a defined End of Primary Support policy associated with all major 
versions. Please refer to the link below for additional details. 
http://www.emc.com/support/rsa/eops/index.htm

SecurCare Online Security Advisories
RSA, The Security Division of EMC, distributes SCOL 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 disclaim 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 or its suppliers be liable for any 
damages whatsoever including direct, indirect, incidental, consequential, loss 
of business profits or special damages, even if RSA or its suppliers have been 
advised of the possibility of such damages. Some states do not allow the 
exclusion or limitation of liability for consequential or incidental damages so 
the foregoing limitation may not apply.

About RSA SecurCare Notes & Security Advisories Subscription
RSA SecurCare Notes & Security Advisories are targeted e-mail messages that RSA 
sends you based on the RSA product family you currently use. If you?d like to 
stop receiving RSA SecurCare Notes & Security Advisories, or if you?d like to 
change which RSA product family Notes & Security Advisories you currently 
receive, log on to RSA SecurCare Online at 
https://knowledge.rsasecurity.com/scolcms/help.aspx?_v=view3. Following the 
instructions on the page, remove the check mark next to the RSA product family 
whose Notes & Security Advisories you no longer want to receive. Click the 
Submit button to save your selection.

Sincerely,
RSA Customer Support
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)

iEYEARECAAYFAlR+DUAACgkQtjd2rKp+ALxKwwCguqfgc46t0ofsl26hqgKDTfyA
9FwAnRGLdfExDYlAVpbHtI7LdFfZieaR
=ZtNO
-----END PGP SIGNATURE-----