This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95.
The following versions were EOL at the time the CVE was created but are
known to be affected: 8.5.0 though 8.5.100. Other EOL versions may also be affected.
Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue.
Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4017-1 | tomcat9 security update |
Debian DSA |
DSA-5845-1 | tomcat10 security update |
EUVD |
EUVD-2024-3331 | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. |
Github GHSA |
GHSA-xcpr-7mr4-h4xq | Apache Tomcat - Authentication Bypass |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 07 Nov 2025 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Debian
Debian debian Linux |
|
| CPEs | cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | |
| Vendors & Products |
Debian
Debian debian Linux |
Mon, 03 Nov 2025 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 29 Oct 2025 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. |
Fri, 08 Aug 2025 11:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. Older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. |
Thu, 07 Aug 2025 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. Older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. |
Wed, 16 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Fri, 06 Jun 2025 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-248 |
Thu, 15 May 2025 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-754 | |
| CPEs | cpe:2.3:a:apache:tomcat:*:*:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone10:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone11:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone12:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone13:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone14:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone15:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone16:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone17:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone18:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone19:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone1:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone20:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone21:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone22:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone23:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone24:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone25:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone26:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone2:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone3:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone4:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone5:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone6:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone7:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone8:*:*:*:*:*:* cpe:2.3:a:apache:tomcat:11.0.0:milestone9:*:*:*:*:*:* |
Wed, 14 May 2025 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat enterprise Linux
|
|
| CPEs | cpe:/o:redhat:enterprise_linux:10.0 | |
| Vendors & Products |
Redhat enterprise Linux
|
Tue, 08 Apr 2025 02:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat jboss Enterprise Web Server |
|
| CPEs | cpe:/a:redhat:jboss_enterprise_web_server:6.1 cpe:/a:redhat:jboss_enterprise_web_server:6.1::el8 cpe:/a:redhat:jboss_enterprise_web_server:6.1::el9 |
|
| Vendors & Products |
Redhat
Redhat jboss Enterprise Web Server |
Fri, 24 Jan 2025 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 22 Nov 2024 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 22 Nov 2024 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 18 Nov 2024 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache tomcat |
|
| CPEs | cpe:2.3:a:apache:tomcat:-:*:*:*:*:*:*:* | |
| Vendors & Products |
Apache
Apache tomcat |
|
| Metrics |
cvssV3_1
|
Mon, 18 Nov 2024 11:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. | |
| Title | Apache Tomcat: Authentication bypass when using Jakarta Authentication API | |
| Weaknesses | CWE-391 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2025-11-04T15:59:51.152Z
Reserved: 2024-11-07T07:41:56.639Z
Link: CVE-2024-52316
Updated: 2025-11-03T20:45:28.908Z
Status : Analyzed
Published: 2024-11-18T12:15:18.600
Modified: 2025-11-07T16:15:59.050
Link: CVE-2024-52316
OpenCVE Enrichment
No data.
Debian DLA
Debian DSA
EUVD
Github GHSA