000036169 - RSA Access Manager Apache Web Agent 5.0.x False Positive Security Vulnerabilities

Document created by RSA Customer Support Employee on Jan 21, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036169
Applies ToRSA Access Manager Apache Web Agent 5.0.x
CVE IDThe CVE IDs are listed in the table below.
Article Summary
This article provides a list of security vulnerabilities that cannot be exploited on RSA Access Manager Apache Web Agent 5.0.x, but which may be identified by security scanners.
Link to AdvisoriesEach CVE ID listed can be searched using the following link: https://web.nvd.nist.gov/view/vuln/search. Once there, you can search for each CVE ID referenced in this article for more details.
Alert ImpactNot Exploitable
Alert Impact ExplanationFalse Positive
ResolutionThe vulnerabilities that are listed in the table below are in order by the date on which RSA Access Manager Engineering determined that the Access Manager Apache Web Agent 5.0.x was not vulnerable.
Embedded ComponentCVE IDSummary of VulnerabilityReason why Product is not VulnerableDate Determined False Positive
Apache httpdCVE-2017-3167In Apache httpd 2.2.x before 2.2.33 and 2.4.x before 2.4.26, use of the ap_get_basic_auth_pw() by third-party modules outside of the authentication phase may lead to authentication requirements being bypassed.The function ap_get_basic_auth_pw() is used by the RSA Access Manager Apache Web Agent during the authentication phase only.3 January, 2018
OpenSSLCVE-2017-3737OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to an issue it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object then it succeeds and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error.  OpenSSL version 1.0.2b-1.0.2m are affected.This vulnerability is with SSL handshake functionality in the OpenSSL library.  The Access Manager Apache Webagent does not use the OpenSSL library.  RSA Access Manager Apache Webagent uses RSA BSAFE Cert-C and RSA BSAFE MES to perform SSL handshakes.13 March, 2018

 

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.

Attachments

    Outcomes