BLACKOUT MAP

Apache · Tomcat

CVE-2020-1938

Apache Tomcat Improper Privilege Management Vulnerability

Bei Angriffen ausgenutzt Kritisch 9,8 Angriffswahrscheinlichkeit: 99,3%
Teilen

Was es ist

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.

CISA: Apache Tomcat treats Apache JServ Protocol (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.

Was zu tun ist

Apply updates per vendor instructions.

Frist für US-Bundesbehörden: 17. März 2022

Zur CISA-Liste hinzugefügt
3. März 2022
Veröffentlicht
24. Februar 2020
Schweregrad
Kritisch 9,8 CVSS 3.1
Wahrscheinlichkeit von Angriffen in den nächsten 30 Tagen (EPSS)
99,3% unter den obersten 0,1% aller bekannten Schwachstellen
Mehr Details
NVD · CVE.org · CISA
Alle Quellen (20)

Weitere ausgenutzte Schwachstellen von Apache

HinzugefügtSchwachstelleProduktSchweregradAngriffswahrscheinlichkeit
04.08.2026Missing Encryption of Sensitive DataCVE-2026-34486TomcatHoch 7,599%
01.04.2025Path EquivalenceCVE-2025-24813TomcatKritisch 10,099,9%
12.05.2023Remote Code ExecutionCVE-2016-8735TomcatKritisch 9,890%
25.03.2022on Windows Remote Code ExecutionCVE-2017-12615von Ransomware genutztTomcatHoch 8,199,7%
25.03.2022Remote Code ExecutionCVE-2017-12617TomcatHoch 8,1>99,9%
08.10.2026Command InjectionCVE-2016-3081StrutsHoch 8,197%
16.04.2026Improper Input ValidationCVE-2026-34197ActiveMQHoch 8,898%
01.05.2025Improper Escaping of OutputCVE-2024-38475HTTP ServerKritisch 9,1>99,9%

Alle →

Quellen: Known Exploited Vulnerabilities (CISA, gemeinfrei), CVE records (cve.org) und EPSS (FIRST). Die Angriffswahrscheinlichkeit ist die EPSS-Schätzung, dass jemand in den nächsten 30 Tagen versucht, die Schwachstelle auszunutzen.