CVE-2020-1935Not scoredCWE-444

CVE-2020-1935: Apache Tomcat vulnerability

Apache · Apache Tomcat

Vendor fix available · Affected: Apache Tomcat · Exploitation: possible (1 to 10%)

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

9.4%probability of exploitation in the next 30 days

95th percentile

050100

Higher than 95% of scored CVEs

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

DescriptionCVE.org

In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.

Affected products1

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

Apache · Apache TomcatApache Tomcat 9.0.0.M1 to 9.0.30; 8.5.0 to 8.5.50; 7.0.0 to 7.0.99

On the Atlas

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

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Inconsistent Interpretation of HTTP Requests · Injection and Smuggling
Vendor: Apache
Published: February 2020
Band: Possible (1 to 10%), February 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-1935 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.

References

7 more references are in the CVE record.