Date: 04 December 2014
Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
ESA-2014-160: RSA Adaptive Authentication (On-Premise)
Authentication Bypass Vulnerability
4 December 2014
AusCERT Security Bulletin Summary
Product: RSA Adaptive Authentication
RSA Adaptive Authentication Integration Adapters
Operating System: Windows
Impact/Access: Unauthorised Access -- Existing Account
CVE Names: CVE-2014-4631
- --------------------------BEGIN INCLUDED TEXT--------------------
ESA-2014-160: RSA Adaptive Authentication (On-Premise) Authentication Bypass
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)
RSA Adaptive Authentication (On-Premise) 22.214.171.124 to 7.1 P3 (inclusive)
RSA Adaptive Authentication Integration Adapters 1.x and 2.x
RSA Adaptive Authentication (Hosted) all versions
RSA Adaptive Authentication (On-Premise) 126.96.36.199 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.
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
In RSA Adaptive Authentication Integration Adapters, a device binding request
is sent in the Challenge SOAP call for Out-of-Band Phone (Authentify)
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
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.
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 youd like to stop
receiving RSA SecurCare Notes & Security Advisories, or if youd 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
- --------------------------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 firstname.lastname@example.org
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
Internet Email: email@example.com
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.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----