What’s Vulnerable › Vulnerabilities
CVE-2020-1938: Apache Tomcat Improper Privilege Management Vulnerability
- Severity: critical (CVSS 9.8 v3.1)
- Exploited in the wild: yes — in CISA KEV since 2022-03-03
- EPSS: 99.3% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2020-02-24 · updated 2026-08-25
Description
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 9.0.0.30, 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 defence-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.
Affected products
- Apache Software Foundation Apache Geode: 1.12.0
- Apache Tomcat: from 7.0.0 before 7.0.100; from 8.5.0 before 8.5.51; from 9.0.0 before 9.0.31 — fixed in 7.0.100, 8.5.51, 9.0.31
- BlackBerry Good Control: through 5.2.58.38
- BlackBerry Workspaces Server: 7.0.1, 7.1.2, 8.1.0, 9.0
- Debian Linux: 8.0, 9.0, 10.0
- Fedoraproject Fedora: 30, 31, 32
- NetApp Data Availability Services: all versions
- OnCommand System Manager 9.x: from 3.0.0 through 3.1.3
- openSUSE Leap: 15.1
- Oracle Corporation Oracle Agile Engineering Data Management: 6.2.1.0
- Oracle Corporation Oracle Agile PLM: 9.3.3, 9.3.5, 9.3.6
- Oracle Communications Element Manager: 8.1.1, 8.2.0, 8.2.1
- Oracle Communications Instant Messaging Server: 10.0.1.4.0
- Oracle Health Sciences Empirica Inspections: 1.0.1.2
- Oracle Health Sciences Empirica Signal: 7.3.3
- Oracle Corporation Hospitality Guest Access: 4.2.0, 4.2.1
- Oracle Instantis Enterprisetrack: from 17.1 through 17.3
- Oracle Corporation MySQL Enterprise Monitor: through 4.0.12; from 8.0.0 through 8.0.20
- Oracle Corporation Siebel UI Framework: through 20.5
- Oracle Corporation Transportation Management: 6.3.7
- Oracle Workload Manager: 12.2.0.1, 18c, 19c
How to fix
Upgrade to a fixed version: Apache Tomcat 7.0.100, 8.5.51, 9.0.31. Check the vendor advisory for mitigations.
References
- http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00025.html
- http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00002.html
- http://support.blackberry.com/kb/articleDetail?articleNumber=000062739
- https://lists.apache.org/thread.html/r089dc67c0358a1556dd279c762c74f32d7a254a54836b7ee2d839d8e%40%3Cdev.tomee.apache.org%3E
- https://lists.apache.org/thread.html/r1125f3044a0946d1e7e6f125a6170b58d413ebd4a95157e4608041c7%40%3Cannounce.apache.org%3E
- https://lists.apache.org/thread.html/r17aaa3a05b5b7fe9075613dd0c681efa60a4f8c8fbad152c61371b6e%40%3Cusers.tomcat.apache.org%3E
- https://lists.apache.org/thread.html/r38a5b7943b9a62ecb853acc22ef08ff586a7b3c66e08f949f0396ab1%40%3Cusers.tomcat.apache.org%3E
- https://lists.apache.org/thread.html/r43faacf64570b1d9a4bada407a5af3b2738b0c007b905f1b6b608c65%40%3Cusers.tomcat.apache.org%3E
- https://lists.apache.org/thread.html/r47caef01f663106c2bb81d116b8380d62beac9e543dd3f3bc2c2beda%40%3Ccommits.tomee.apache.org%3E
- https://lists.apache.org/thread.html/r4afa11e0464408e68f0e9560e90b185749363a66398b1491254f7864%40%3Cusers.tomcat.apache.org%3E
- https://lists.apache.org/thread.html/r4f86cb260196e5cfcbbe782822c225ddcc70f54560f14a8f11c6926f%40%3Cusers.tomcat.apache.org%3E
- https://lists.apache.org/thread.html/r549b43509e387a42656f0641fa311bf27c127c244fe02007d5b8d6f6%40%3Cdev.tomcat.apache.org%3E
Get alerted when CVE-2020-1938 or the next vulnerability affects your stack