KM03634338 - Service Management Automation (SMA). Apache Tomcat vulnerability CVE-2020-1938.

  • KM03634338
  • 15-Apr-2020
  • 15-Apr-2020


A vulnerability in the Apache Tomcat components used by SMA products was addressed by the Micro Focus Service Management Automation (SMA) R&D team. 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 by intentional design 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. For more details on this issue, please reference the CVE ID and link below:



Potential Security Impact: File content disclosure / remote code execution in Apache Tomcat  



A vulnerability in the Apache Tomcat components used by SMA products was addressed by the Micro Focus Service Management Automation (SMA) R&D team. 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 by intentional design 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. For more details on this issue, please reference the CVE ID and link below: 

CVE References: 



SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed. 

2020.02, 2019.11, 2019.08, 2019.05, 2019.02, 2018.08, 2018.05, 2018.02 


CVSS Version 3.0 and Version 2.0 Base Metrics 


V3 Vector 

V3 Base Score 

V2 Vector 

V2 Base Score 









Micro Focus has made the following mitigation information available to resolve the vulnerability for the impacted versions of SMA. These manual instructions are necessary and should be applied in affected environments. The instructions will disable the vulnerable AJP port. Please note that Micro Focus will release a future version of the product which will not require the manual application of the following instructions. 


In order to disable the AJP port, login to a Master node of the CDF Kubernetes cluster and copy/paste the following command to run it on the node: 

# kubectl patch deployment idm -n core --patch '{"spec": {"template": {"spec": {"containers": [{"name": "idm","command": ["sh", "-c", "sed -i /port=\\\"8009\\\"/d /opt/apache-tomcat/conf/server.xml \u0026\u0026  /"]}]}}}}' 

The previous command will restart the CDF IDM pods automatically with AJP disabled to prevent the vulnerability. 

In addition, the following commands must also be run to mitigate the remaining affected Suite (SMA) components. The commands, like those above, will restart the pods as needed with AJP disabled. 

Before running the commands below, find the relevant Kubernetes namespace by running the following command: 

# kubectl get namespaces | grep itsma | awk '{print $1}' 

You must substitute <itsma_namespace>  with the actual namespace value provided by the previous command. 

# kubectl patch deployment idm -n <itsma_namespace> --patch '{"spec": {"template": {"spec": {"containers": [{"name": "idm","command": ["sh", "-c", "sed -i /port=\\\"8009\\\"/d /opt/apache-tomcat/conf/server.xml \u0026\u0026  /"]}]}}}}' 

# kubectl patch deployment auth -n <itsma_namespace> --patch '{"spec": {"template": {"spec": {"containers": [{"name": "auth","command": ["sh", "-c", "sed -i /port=\\\"8009\\\"/d /opt/tomcat/conf/server.xml \u0026\u0026  /"]}]}}}}' 

# kubectl patch deployment ucmdb-browser -n <itsma_namespace> --patch '{"spec": {"template": {"spec": {"containers": [{"name": "ucmdb-browser","command": ["sh", "-c", "sed -i /port=\\\"8009\\\"/d /usr/local/tomcat/conf/server.xml \u0026\u0026  /usr/local/tomcat/entrypoint/"]}]}}}}' 

Finally, for customers running older versions 2018.02, 2018.05 and 2018.08 in “H mode”, you must run the following commands as well: 

# kubectl patch deployment sm-webtier -n <itsma_namespace> --patch '{"spec": {"template": {"spec": {"containers": [{"name": "sm-webtier","command": ["sh", "-c", "sed -i /port=\\\"8009\\\"/d /opt/tomcat/conf/server.xml \u0026\u0026  /"]}]}}}}'  

# kubectl patch deployment sm-mobility -n <itsma_namespace> --patch '{"spec": {"template": {"spec": {"containers": [{"name": "sm-mobility","command": ["sh", "-c", "sed -i /port=\\\"8009\\\"/d /opt/tomcat/conf/server.xml \u0026\u0026  /"]}]}}}}' 


NOTE: The above instructions will not need to be applied after Micro Focus releases newer versions of the product. 


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:

·         Email:


Subscribe: To initiate receiving subscriptions for future Micro Focus Security Bulletin alerts via Email, please subscribe here - 
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

Security Bulletin Archive: A list of recently released Security Bulletins is available here:

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.