ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Impact of Ghostcat (CVE-2020-1938) with Service Management r17.x
Article ID: 186049
CA Service Desk ManagerSUPPORT AUTOMATION- SERVERCA Service Desk Manager - Unified Self ServiceKNOWLEDGE TOOLSCA Service Desk Manager - Mobile ApplicationCA Service Desk Manager - XtractionCA Service CatalogCA IT Asset ManagerCA IT Asset Manager Asset Portfolio Management
We do not depend on AJP protocol out of the box in Service Desk Manager. Service Catalog's might be used when its made part of out of the box cluster configuration.
AJP connector can be disabled so that the exposure of this vulnerability does not happen.
Commenting of the AJP connector can be done like indicated in below example on any Tomcat's server.xml files.
Below indicates that the connector is commented out. <!-- Define an AJP 1.3 Connector on port 8009 --> <!-- <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" xpoweredBy="false" allowTrace="false"></Connector> -->
If AJP Connector cannot be disabled and needs to be used (example: Catalog Cluster configuration), you can configure the “requiredSecret” attribute for the AJP Connector to set AJP protocol authentication credentials. For example (YOUR_TOMCAT_AJP_SECRET is your password)