Skip to content

GHSA-f268-65qc-98vg BIT-tomcat-2020-13943 CVE-2020-13943

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Medium Maven
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
52.64%
Chance of exploitation in the next 30 days. Higher than 98.97% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
10.0.0-M8
Upgrade org.apache.tomcat:tomcat-coyote to this version or later

Description

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 versions

Maven

PackageVulnerableFixed in
org.apache.tomcat:tomcat-coyote
>= 10.0.0-M1, < 10.0.0-M8
10.0.0-M8
org.apache.tomcat:tomcat-coyote
>= 9.0.0-M1, < 9.0.38
9.0.38
org.apache.tomcat:tomcat-coyote
>= 8.5.0, < 8.5.58
8.5.58

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.tomcat:tomcat-coyote Maven → 10.0.0-M8

maven
<dependency><groupId>org.apache.tomcat</groupId><artifactId>tomcat-coyote</artifactId><version>10.0.0-M8</version></dependency>
gradle
implementation("org.apache.tomcat:tomcat-coyote:10.0.0-M8")

Severity breakdown

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

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

How to prevent it
  • Architecture and Design: 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

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-qppj-fm5r-hxr3
HTTP/2 Stream Cancellation Attack
Medium Known exploited Also affects org.apache.tomcat:tomcat-coyote
GHSA-f525-44xv-f2qj
Apache Tomcat - HTTP/2 no-authority bypass of strict SNI validation
Critical Also affects org.apache.tomcat:tomcat-coyote
GHSA-r29c-68gh-xp6x
Apache Tomcat - HTTP/2 request headers not validated
Critical Also affects org.apache.tomcat:tomcat-coyote
GHSA-8mc5-53m5-3qj2
Apache Tomcat has an Improper Input Validation vulnerability
Medium Also affects org.apache.tomcat:tomcat-coyote
GHSA-69cc-cv78-qc8g
Apache Tomcat: Configured cipher preference order not preserved
High Also affects org.apache.tomcat:tomcat-coyote
GHSA-563x-q5rq-57qp
Apache Tomcat has an HTTP Request/Response Smuggling vulnerability
High Also affects org.apache.tomcat:tomcat-coyote
GHSA-mgp5-rv84-w37q
Apache Tomcat has an Improper Input Validation vulnerability
High Also affects org.apache.tomcat:tomcat-coyote
GHSA-qq5r-98hh-rxc9
Apache Tomcat - Security constraint bypass with HTTP/0.9
Low Also affects org.apache.tomcat:tomcat-coyote
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor