KEVIntel

CVE-2020-1938

Confirmed PUBLISHED

When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections...

Apache · Apache Tomcat
Exploited in the wild PoC available

Recommended Action

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

View KEV Feed Talk to Sales
Confidence
Confirmed
Exploitation Status
Exploited in the wild
Observed in Sensors
No
Attempts (30d)
—
Unique Attacker IPs
—
CISA KEV
In CISA KEV
CVSS / EPSS
9.8 Critical

At a Glance

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 nuclei_scanner
CVE Published
Feb 24, 2020
Exploitation Reported
Mar 03, 2022
CVSS
9.8 Critical
EPSS
—
Remote Low complexity No user interaction Unauthenticated

Affected Versions

Vendor Product Version Status
Apache
Apache Tomcat

Apache Tomcat 9.0.0.M1 to 9.0.0.30

 Affected
Apache
Apache Tomcat

8.5.0 to 8.5.50

 Affected
Apache
Apache Tomcat

7.0.0 to 7.0.99

 Affected

CVE References

  • openSUSE-SU-2020:0345 lists.opensuse.org · Vendor Advisory http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00025...
  • GLSA-202003-43 security.gentoo.org · Vendor Advisory https://security.gentoo.org/glsa/202003-43
  • FEDORA-2020-0e42878ba7 lists.fedoraproject.org · Vendor Advisory https://lists.fedoraproject.org/archives/list/package-announce%40list...
  • FEDORA-2020-c870aa8378 lists.fedoraproject.org · Vendor Advisory https://lists.fedoraproject.org/archives/list/package-announce%40list...
  • FEDORA-2020-04ac174fa9 lists.fedoraproject.org · Vendor Advisory https://lists.fedoraproject.org/archives/list/package-announce%40list...
Show 46 more references

Recommended Actions

  • Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
  • Check enrichment artifacts for scanner coverage and available PoCs before rolling remediation validation.
  • Use the Pro API to automate enrichment, telemetry, and workflow delivery for VM, SOC, and CTI pipelines.