CVE-2020-13943

CVE-2020-13943: vulnerability in Apache Tomcat

Published · Updated

Follow this CVE+ Monitor Apache Tomcat+ Monitor tomcat9

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

15Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 53%
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Affected
7 products (19 components)
Red Hat Enterprise Linux 6 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 5 · Red Hat JBoss Data Grid 6 · Red Hat JBoss Data Virtualization 6 · and others 2
no_fix_planned: Out of support scope
Fixed
5 products (31 components)
Red Hat JBoss Web Server 5.4 for RHEL 7 Server · Red Hat JBoss Web Server 5.4 for RHEL 8 · Red Hat Fuse 7.10 · Red Hat JBoss Web Server 5 · Red Hat Support for Spring Boot 2.4.9
fix ↗
Not affected
7 products (22 components) — because the vulnerable code is not present in the product
Red Hat Enterprise Linux 7 · Red Hat Software Collections · Red Hat OpenStack Platform 13 (Queens) · Red Hat Decision Manager 7 · Red Hat JBoss Web Server 3 · and others 2
If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
Affected products
n/a · Apache Tomcat