CVE-2020-13934

CVE-2020-13934: vulnerability in Apache Tomcat

Published · Updated

15Vexday Risk Score

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

ssvc Trackepss 64%
exploitation probability
64%top 1% of all CVEs
observed exploitation
nono source reports it
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.

Affected
6 products (8 components)
Red Hat Enterprise Linux 8 · Red Hat JBoss Data Grid 6 · Red Hat JBoss Data Virtualization 6 · Red Hat JBoss Enterprise Application Platform 6 · Red Hat JBoss Fuse 6 · and others 1
none_available: Fix deferred
Fixed
6 products (36 components)
Red Hat JBoss Web Server 5.3 for RHEL 6 Server · Red Hat JBoss Web Server 5.3 for RHEL 7 Server · Red Hat JBoss Web Server 5.3 for RHEL 8 · Red Hat Fuse 7.9 · Red Hat JBoss Web Server (JWS) 5.3 · and others 1
Not affected
8 products (41 components) — because the vulnerable code is not present in the product
Red Hat Enterprise Linux 6 · Red Hat Enterprise Linux 7 · Red Hat Enterprise Linux 9 · Red Hat Software Collections · Red Hat OpenStack Platform 13 (Queens) · and others 3
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
Affected products
n/a · Apache Tomcat