SUPPORT COMMUNICATION - SECURITY BULLETIN
Potential Security Impact: File content disclosure / remote code execution in Apache Tomcat
A vulnerability in Apache Tomcat was addressed by Network Automation. The vulnerability could be exploited to file content disclosure of the web application or remote code execution.
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 184.108.40.206, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defense-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.
SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed.
Network Automation Affected Versions:
9.2x, 10.0x, 10.1x, 10.2x, 10.3x, 10.4x, 10.5x, 2018.05, 2018.08, 2018.11,2019.05.
Only the environments that have deployed Network Automation Gateway/Satellite component are impacted.
CVSS Version 3.0 and Version 2.0 Base Metrics
V3 Base Score
V2 Base Score
Micro Focus has made the following mitigation information available to resolve the vulnerability for the impacted versions of Network Automation:
To check if you have deployed NA Gateway/Satellite Remote Agents:
You can find list of Remote Gateways by Logging into the NA Web UI and going to Menu:
Admin -> Gateways.
If you get a message âThere is no Gateway Mesh configured.â then you are not affected.
If you get a table with Gateway list, if you find any row with the Agent column filled in, then you are affected.
If you have deployed Network Automation Satellite:
1. On each Remote Gateway server, login to the machine.
o You can find list of Remote Gateways by Logging into the NA Web UI and going to Menu:
Admin -> Gateways.
Machines with âAgentâ column value filled in, are Remote Gateways with NA Satellite Remote Agent installed.
2. Stop the NA Satellite Remote Agent Component using:
3. Take a backup of the file: /opt/opsware/nassat/server/ext/tomcat/conf/server.xml to a location outside the /opt/ directory structure.
4. Open the File /opt/opsware/nassat/server/ext/tomcat/conf/server.xml
And DELETE the following two lines:
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
5. Restart the NA Satellite Remote Agent Component using:
Note: If you redeploy the NA Satellite Remote Agent on affected versions of NA, you will need to redo the steps 1-5.
Note: Please ignore the following message you might get when stopping NA Satellite Remote Agent:
rm: cannot remove â/var/run/catalina.pidâ: No such file or directory
You can alternatively mitigate this issue if you upgrade to an unaffected version.
Network Automation Versions that are unaffected:
Third Party Security Patches: Third party security patches that are to be installed on systems running Micro Focus software products should be applied in accordance with the customer's patch management policy.
Support: For issues about implementing the recommendations of this Security Bulletin, contact normal Micro Focus services support channel. For other issues about the content of this Security Bulletin, send e-mail to Product Security Team.
Report: To report a potential security vulnerability for any supported product:
Â· Web Form: https://mysupport.microfocus.com/psrt
Â· Email: email@example.com
Subscribe: To initiate receiving subscriptions for future Micro Focus Security Bulletin alerts via Email, please subscribe here - https://mysupport.microfocus.com/group/softwaresupport/email-notification/-/subscriptions/registerdocumentnotification
Once you are logged in to the portal, please choose security bulletins under âproductâ and âdocument typesâ.
Please note that you will need to sign in using a Passport account. If you do not have a Passport account yet, you can create one- itâs free and easy https://www.microfocus.com/selfreg/jsp/createAccount.jsp
Security Bulletin Archive: A list of recently released Security Bulletins is available here: https://mysupport.microfocus.com/security-vulnerability
Software Product Category: The Software Product Category is represented in the title by the two characters following Micro Focus Security Bulletin.
3P = 3rd Party Software
GN = Micro Focus General Software
MU = Multi-Platform Software
System management and security procedures must be reviewed frequently to maintain system integrity. Micro Focus is continually reviewing and enhancing the security features of software products to provide customers with current secure solutions.
"Micro Focus is broadly distributing this Security Bulletin in order to bring to the attention of users of the affected Micro Focus products the important security information contained in this Bulletin. Micro Focus recommends that all users determine the applicability of this information to their individual situations and take appropriate action. Micro Focus does not warrant that this information is necessarily accurate or complete for all user situations and, consequently, Micro Focus will not be responsible for any damages resulting from user's use or disregard of the information provided in this Security Bulletin. To the extent permitted by law, Micro Focus disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose, title and non-infringement."
Â© Copyright Micro Focus
Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither Micro Focus nor its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Micro Focus and the names of Micro Focus products referenced herein are trademarks of Micro Focus in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.