CVE-2020-13943Not scored

CVE-2020-13943: Apache Tomcat vulnerability

Apache · Apache Tomcat

Vendor fix available · Affected: Apache Tomcat · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

52.6%probability of exploitation in the next 30 days

98th percentile

050100

Higher than 98% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Apache TomcatApache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37, 8…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Vendor: Apache
Published: October 2020
Band: Likely to be exploited (10% or more), October 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-13943 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.