EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB484091: Addressing the Apache Tomcat JServ Protocol (AJP) Security Vulnerability


Community Admin

• Strategy


This article explains a recent security flaw identified in the Apache Tomcat AJP connector.

On February 27, 2020, the National Vulnerability Database disclosed that a critical security flaw has existed in Apache Tomcat for the past 13 years. The details of this flaw, commonly referred to as Ghostcat, are available in CVE-2020-1938.
This vulnerability was identified in the Apache Tomcat AJP connector, which is used to process the AJP V1.3 protocol. If exploited, this vulnerability would allow an attacker to read the contents of configuration files and source code files of all webapps deployed on Tomcat. This vulnerability could also make it possible for an attacker to remotely execute an uploaded file.
The Tomcat AJP connector enables Catalina, the Tomcat servlet container, to receive external requests and pass them to a web application for processing, and to return the results of a request.
Although Strategy versions 2020, 2019, and 10.4.8 support Tomcat for Strategy Mobile Servers, Strategy Web, and the Strategy Library Server and Rest Server, Strategy does not require the use of this connector or the AJP protocol. 
Apache Tomcat has fixed the AJP security flaw in all supported versions. As such, Strategy urges all customers who rely on Tomcat for their Strategy deployments to upgrade their installations to the latest non-vulnerable version of Tomcat. Additionally, since AJP uses listening address

0.0.0.0:8009
by default, Strategy strongly advises customers to evaluate services associated with port
8009 
in their Tomcat configurations.
For Strategy Cloud (MCE and MCP), the AJP port has been blocked thereby preventing exploitation of this vulnerability.
Please see Apache Tomcat Versions for instructions on installing and configuring the correct version of Tomcat.
For customers who require the use of the AJP port, see KB484096: Setting up the AJP port on Tomcat and Apache Servers for steps on how to set up the AJP port on Tomcat and Apache Servers to avoid the vulnerability.

References

ZDNet article
Red Hat (including JBOSS).


Comment

0 comments

Details

Knowledge Article

Published:

March 2, 2020

Last Updated:

March 4, 2020