CVE Vulnerabilities

CVE-2020-13934

Missing Release of Memory after Effective Lifetime

Published: Jul 14, 2020 | Modified: Nov 07, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

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.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Affected Software

Name Vendor Start Version End Version
Tomcat Apache 8.5.1 (including) 8.5.56 (including)
Tomcat Apache 9.0.1 (including) 9.0.36 (including)
Tomcat Apache 9.0.0-milestone10 (including) 9.0.0-milestone10 (including)
Tomcat Apache 9.0.0-milestone11 (including) 9.0.0-milestone11 (including)
Tomcat Apache 9.0.0-milestone12 (including) 9.0.0-milestone12 (including)
Tomcat Apache 9.0.0-milestone13 (including) 9.0.0-milestone13 (including)
Tomcat Apache 9.0.0-milestone14 (including) 9.0.0-milestone14 (including)
Tomcat Apache 9.0.0-milestone15 (including) 9.0.0-milestone15 (including)
Tomcat Apache 9.0.0-milestone16 (including) 9.0.0-milestone16 (including)
Tomcat Apache 9.0.0-milestone17 (including) 9.0.0-milestone17 (including)
Tomcat Apache 9.0.0-milestone18 (including) 9.0.0-milestone18 (including)
Tomcat Apache 9.0.0-milestone19 (including) 9.0.0-milestone19 (including)
Tomcat Apache 9.0.0-milestone20 (including) 9.0.0-milestone20 (including)
Tomcat Apache 9.0.0-milestone21 (including) 9.0.0-milestone21 (including)
Tomcat Apache 9.0.0-milestone22 (including) 9.0.0-milestone22 (including)
Tomcat Apache 9.0.0-milestone23 (including) 9.0.0-milestone23 (including)
Tomcat Apache 9.0.0-milestone24 (including) 9.0.0-milestone24 (including)
Tomcat Apache 9.0.0-milestone25 (including) 9.0.0-milestone25 (including)
Tomcat Apache 9.0.0-milestone26 (including) 9.0.0-milestone26 (including)
Tomcat Apache 9.0.0-milestone27 (including) 9.0.0-milestone27 (including)
Tomcat Apache 9.0.0-milestone5 (including) 9.0.0-milestone5 (including)
Tomcat Apache 9.0.0-milestone6 (including) 9.0.0-milestone6 (including)
Tomcat Apache 9.0.0-milestone7 (including) 9.0.0-milestone7 (including)
Tomcat Apache 9.0.0-milestone8 (including) 9.0.0-milestone8 (including)
Tomcat Apache 9.0.0-milestone9 (including) 9.0.0-milestone9 (including)
Tomcat Apache 10.0.0-milestone1 (including) 10.0.0-milestone1 (including)
Tomcat Apache 10.0.0-milestone2 (including) 10.0.0-milestone2 (including)
Tomcat Apache 10.0.0-milestone3 (including) 10.0.0-milestone3 (including)
Tomcat Apache 10.0.0-milestone4 (including) 10.0.0-milestone4 (including)
Tomcat Apache 10.0.0-milestone5 (including) 10.0.0-milestone5 (including)
Tomcat Apache 10.0.0-milestone6 (including) 10.0.0-milestone6 (including)
Red Hat Fuse 7.9 RedHat tomcat *
Red Hat JBoss Web Server 5.3 on RHEL 6 RedHat jws5-tomcat-0:9.0.30-5.redhat_6.1.el6jws *
Red Hat JBoss Web Server 5.3 on RHEL 7 RedHat jws5-tomcat-0:9.0.30-5.redhat_6.1.el7jws *
Red Hat JBoss Web Server 5.3 on RHEL 8 RedHat jws5-tomcat-0:9.0.30-5.redhat_6.1.el8jws *
Red Hat JBoss Web Server (JWS) 5.3 RedHat tomcat *
Red Hat Runtimes Spring Boot 2.2.6 RedHat tomcat *
Tomcat6 Ubuntu precise/esm *
Tomcat6 Ubuntu trusty *
Tomcat6 Ubuntu xenial *
Tomcat7 Ubuntu bionic *
Tomcat7 Ubuntu trusty *
Tomcat7 Ubuntu xenial *
Tomcat8 Ubuntu bionic *
Tomcat9 Ubuntu bionic *
Tomcat9 Ubuntu eoan *
Tomcat9 Ubuntu focal *

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References