Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2021-25122

Exposure of Sensitive Information to an Unauthorized Actor

Published: Mar 01, 2021 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2021-25122
CWEhttps://cwe.mitre.org/data/definitions/200.html

When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user As request.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

NameVendorStart VersionEnd Version
TomcatApache8.5.0 (including)8.5.61 (including)
TomcatApache9.0.0 (including)9.0.41 (including)
TomcatApache9.0.0-milestone1 (including)9.0.0-milestone1 (including)
TomcatApache9.0.0-milestone10 (including)9.0.0-milestone10 (including)
TomcatApache9.0.0-milestone11 (including)9.0.0-milestone11 (including)
TomcatApache9.0.0-milestone12 (including)9.0.0-milestone12 (including)
TomcatApache9.0.0-milestone13 (including)9.0.0-milestone13 (including)
TomcatApache9.0.0-milestone14 (including)9.0.0-milestone14 (including)
TomcatApache9.0.0-milestone15 (including)9.0.0-milestone15 (including)
TomcatApache9.0.0-milestone16 (including)9.0.0-milestone16 (including)
TomcatApache9.0.0-milestone17 (including)9.0.0-milestone17 (including)
TomcatApache9.0.0-milestone18 (including)9.0.0-milestone18 (including)
TomcatApache9.0.0-milestone19 (including)9.0.0-milestone19 (including)
TomcatApache9.0.0-milestone2 (including)9.0.0-milestone2 (including)
TomcatApache9.0.0-milestone20 (including)9.0.0-milestone20 (including)
TomcatApache9.0.0-milestone21 (including)9.0.0-milestone21 (including)
TomcatApache9.0.0-milestone22 (including)9.0.0-milestone22 (including)
TomcatApache9.0.0-milestone23 (including)9.0.0-milestone23 (including)
TomcatApache9.0.0-milestone24 (including)9.0.0-milestone24 (including)
TomcatApache9.0.0-milestone25 (including)9.0.0-milestone25 (including)
TomcatApache9.0.0-milestone26 (including)9.0.0-milestone26 (including)
TomcatApache9.0.0-milestone27 (including)9.0.0-milestone27 (including)
TomcatApache9.0.0-milestone3 (including)9.0.0-milestone3 (including)
TomcatApache9.0.0-milestone4 (including)9.0.0-milestone4 (including)
TomcatApache9.0.0-milestone5 (including)9.0.0-milestone5 (including)
TomcatApache10.0.0 (including)10.0.0 (including)
TomcatApache10.0.0-milestone1 (including)10.0.0-milestone1 (including)
TomcatApache10.0.0-milestone10 (including)10.0.0-milestone10 (including)
TomcatApache10.0.0-milestone2 (including)10.0.0-milestone2 (including)
TomcatApache10.0.0-milestone3 (including)10.0.0-milestone3 (including)
TomcatApache10.0.0-milestone4 (including)10.0.0-milestone4 (including)
TomcatApache10.0.0-milestone5 (including)10.0.0-milestone5 (including)
TomcatApache10.0.0-milestone6 (including)10.0.0-milestone6 (including)
TomcatApache10.0.0-milestone7 (including)10.0.0-milestone7 (including)
TomcatApache10.0.0-milestone8 (including)10.0.0-milestone8 (including)
TomcatApache10.0.0-milestone9 (including)10.0.0-milestone9 (including)
Red Hat Fuse 7.11RedHattomcat*
Red Hat JBoss Web Server 5RedHattomcat*
Red Hat JBoss Web Server 5.5 on RHEL 7RedHatjws5-ecj-0:4.12.0-3.redhat_2.2.el7jws*
Red Hat JBoss Web Server 5.5 on RHEL 7RedHatjws5-mod_cluster-0:1.4.3-2.Final_redhat_00002.1.el7jws*
Red Hat JBoss Web Server 5.5 on RHEL 7RedHatjws5-tomcat-0:9.0.43-11.redhat_00011.1.el7jws*
Red Hat JBoss Web Server 5.5 on RHEL 7RedHatjws5-tomcat-native-0:1.2.26-3.redhat_3.el7jws*
Red Hat JBoss Web Server 5.5 on RHEL 7RedHatjws5-tomcat-vault-0:1.1.8-2.Final_redhat_00003.1.el7jws*
Red Hat JBoss Web Server 5.5 on RHEL 8RedHatjws5-ecj-0:4.12.0-3.redhat_2.2.el8jws*
Red Hat JBoss Web Server 5.5 on RHEL 8RedHatjws5-mod_cluster-0:1.4.3-2.Final_redhat_00002.1.el8jws*
Red Hat JBoss Web Server 5.5 on RHEL 8RedHatjws5-tomcat-0:9.0.43-11.redhat_00011.1.el8jws*
Red Hat JBoss Web Server 5.5 on RHEL 8RedHatjws5-tomcat-native-0:1.2.26-3.redhat_3.el8jws*
Red Hat JBoss Web Server 5.5 on RHEL 8RedHatjws5-tomcat-vault-0:1.1.8-2.Final_redhat_00003.1.el8jws*
Red Hat support for Spring Boot 2.3.10RedHattomcat*
Tomcat6Ubuntuprecise/esm*
Tomcat6Ubuntutrusty*
Tomcat6Ubuntuxenial*
Tomcat7Ubuntubionic*
Tomcat7Ubuntutrusty*
Tomcat7Ubuntuxenial*
Tomcat8Ubuntubionic*
Tomcat8Ubuntuesm-apps/bionic*
Tomcat9Ubuntubionic*
Tomcat9Ubuntuesm-apps/bionic*
Tomcat9Ubuntuesm-apps/focal*
Tomcat9Ubuntufocal*
Tomcat9Ubuntugroovy*
Tomcat9Ubuntuhirsute*
Tomcat9Ubuntuimpish*
Tomcat9Ubuntukinetic*
Tomcat9Ubuntulunar*
Tomcat9Ubuntumantic*

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use