Apache · Apache Tomcat · published 2020-02-24
CVE-2020-1938Apache Tomcat Improper Privilege Management Vulnerability
Patch today Known exploited server software, exploitation is automatable, total technical impact.
CVE-2020-1938 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2022-03-03. EPSS estimates a 99.3% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This Apache Tomcat vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Patched packages are out for Debian and Red Hat Enterprise Linux. US federal agencies must remediate by 2022-03-17. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply updates per vendor instructions. (federal due date 2022-03-17)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | tomcat9 | Fixed in 9.0.31-1 |
| 12 bookworm | tomcat9 | Fixed in 9.0.31-1 | |
| Red Hat Enterprise Linux | RHEL 7 | tomcat | Fixed in 7.0.76-11.el7_7 RHSA-2020:0855 |
| RHEL 6 | tomcat6 | Fixed in 6.0.24-114.el6_10 RHSA-2020:0912 | |
| RHEL 5 | tomcat5 | Won’t fix |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
App serverApache Tomcat
Improper Privilege ManagementCVE-2020-1938
Why: Known exploited server software, exploitation is automatable, total technical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2022-03-03 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 99% (100th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
More from this vendor: all Apache vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Apache Apache Tomcat
Apache Tomcat 9.0.0.M1 to 9.0.0.30(affected)8.5.0 to 8.5.50(affected)7.0.0 to 7.0.99(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.