Low Apache Tomcat CVEs
12 CVEs, 2 protected by Waratek
Overview 12 matches · 2 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
2
16.7%
Rule in development
0
0.0%
Mitigation candidate
1
8.3%
No exploit published
9
75.0%
blocked by ARMR today
2
16.7%
partly blocked
0
0.0%
not blocked
10
83.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
16.7%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
10
83.3%
split by
peak 3 / year
20051
No exploit published1
Low1
not blocked1
No public exploit1
20060
20073
Protected by Waratek1
No exploit published2
Low3
blocked by ARMR today1
not blocked2
Working exploit published1
No public exploit2
20080
20091
No exploit published1
Low1
not blocked1
No public exploit1
20101
Mitigation candidate1
Low1
not blocked1
Working exploit published1
20112
Protected by Waratek1
No exploit published1
Low2
blocked by ARMR today1
not blocked1
No public exploit2
20121
No exploit published1
Low1
not blocked1
No public exploit1
20130
20141
No exploit published1
Low1
not blocked1
No public exploit1
20150
20160
20170
20180
20190
20200
20210
20221
No exploit published1
Low1
not blocked1
No public exploit1
20230
20240
20250
20261
No exploit published1
Low1
not blocked1
No public exploit1
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-43514 | Low | 2026-05-12 | No exploit published | No public exploit | Observable Timing Discrepancy vulnerability when comparing AJP secret in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Older unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.22, 10.1.55 or 9.0.118 which fix the issue. |
| CVE-2021-43980 | Low | 2022-09-28 | No exploit published | No public exploit | The simplified implementation of blocking reads and writes introduced in Tomcat 10 and back-ported to Tomcat 9.0.47 onwards exposed a long standing (but extremely hard to trigger) concurrency bug in Apache Tomcat 10.1.0 to 10.1.0-M12, 10.0.0-M1 to 10.0.18, 9.0.0-M1 to 9.0.60 and 8.5.0 to 8.5.77 that could cause client connections to share an Http11Processor instance resulting in responses, or part responses, to be received by the wrong client. |
| CVE-2013-0346 | Low | 2014-02-15 | No exploit published | No public exploit | Apache Tomcat 7.x uses world-readable permissions for the log directory and its files, which might allow local users to obtain sensitive information by reading a file. NOTE: One Tomcat distributor has stated "The tomcat log directory does not contain any sensitive information." |
| CVE-2012-4534 | Low | 2012-12-19 | No exploit published | No public exploit | org/apache/tomcat/util/net/NioEndpoint.java in Apache Tomcat 6.x before 6.0.36 and 7.x before 7.0.28, when the NIO connector is used in conjunction with sendfile and HTTPS, allows remote attackers to cause a denial of service (infinite loop) by terminating the connection during the reading of a response. |
| CVE-2011-2204 | Low | 2011-06-29 | No exploit published | No public exploit | Apache Tomcat 5.5.x before 5.5.34, 6.x before 6.0.33, and 7.x before 7.0.17, when the MemoryUserDatabase is used, creates log entries containing passwords upon encountering errors in JMX user creation, which allows local users to obtain sensitive information by reading a log file. |
| CVE-2010-3718 | Low | 2011-02-10 | Protected by Waratek | No public exploit | Apache Tomcat 7.0.0 through 7.0.3, 6.0.x, and 5.5.x, when running within a SecurityManager, does not make the ServletContext attribute read-only, which allows local web applications to read or write files outside of the intended working directory, as demonstrated using a directory traversal attack. |
| CVE-2010-1157 | Low | 2010-04-23 | Mitigation candidate | Working exploit published | Apache Tomcat 5.5.0 through 5.5.29 and 6.0.0 through 6.0.26 might allow remote attackers to discover the server's hostname or IP address by sending a request for a resource that requires (1) BASIC or (2) DIGEST authentication, and then reading the realm field in the WWW-Authenticate header in the reply. |
| CVE-2008-4308 | Low | 2009-02-26 | No exploit published | No public exploit | The doRead method in Apache Tomcat 4.1.32 through 4.1.34 and 5.5.10 through 5.5.20 does not return a -1 to indicate when a certain error condition has occurred, which can cause Tomcat to send POST content from one request to a different request. |
| CVE-2007-5461 | Low | 2007-10-15 | Protected by Waratek | Working exploit published | Absolute path traversal vulnerability in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0, 5.0.0, 5.5.0 through 5.5.25, and 6.0.0 through 6.0.14, under certain configurations, allows remote authenticated users to read arbitrary files via a WebDAV write request that specifies an entity with a SYSTEM tag. |
| CVE-2007-2450 | Low | 2007-06-14 | No exploit published | No public exploit | Multiple cross-site scripting (XSS) vulnerabilities in the (1) Manager and (2) Host Manager web applications in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0 through 4.1.36, 5.0.0 through 5.0.30, 5.5.0 through 5.5.24, and 6.0.0 through 6.0.13 allow remote authenticated users to inject arbitrary web script or HTML via a parameter name to manager/html/upload, and other unspecified vectors. |
| CVE-2007-1358 | Low | 2007-05-10 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in certain applications using Apache Tomcat 4.0.0 through 4.0.6 and 4.1.0 through 4.1.34 allows remote attackers to inject arbitrary web script or HTML via crafted "Accept-Language headers that do not conform to RFC 2616". |
| CVE-2005-3164 | Low | 2005-10-06 | No exploit published | No public exploit | The AJP connector in Apache Tomcat 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36, as used in Hitachi Cosminexus Application Server and standalone, does not properly handle when a connection is broken before request body data is sent in a POST request, which can lead to an information leak when "unsuitable request body data" is used for a different request, possibly related to Java Servlet pages. |