CVE-2024-52316

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.

CVSS v3 9.8 CRITICAL

9.8^/10

CVSS v3 : CRITICAL

Vector :

Exploitability : 3.9 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://lists.apache.org/thread/lopzlqh91jj9n334g02om08sbysdb928
http://www.openwall.com/lists/oss-security/2024/11/18/2
https://security.netapp.com/advisory/ntap-20250124-0003/

Configurations

No configuration.

History

24 Jan 2025, 20:15

Type	Values Removed	Values Added
References		() https://security.netapp.com/advisory/ntap-20250124-0003/ -

Information

Published : 2024-11-18 12:15

Updated : 2025-01-24 20:15

NVD link : CVE-2024-52316

Mitre link : CVE-2024-52316

CVE.ORG link : CVE-2024-52316

JSON object : View

Products Affected

No product.

CWE

CWE-391

Unchecked Error Condition

{"id": "CVE-2024-52316", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2024-11-18T12:15:18.600", "references": [{"url": "https://lists.apache.org/thread/lopzlqh91jj9n334g02om08sbysdb928", "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2024/11/18/2", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.netapp.com/advisory/ntap-20250124-0003/", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-391"}]}], "descriptions": [{"lang": "en", "value": "Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC)\u00a0ServerAuthContext 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\u00a0Authentication components that behave in this way.\n\nThis 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.\n\nUsers are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue."}, {"lang": "es", "value": "Vulnerabilidad de condici\u00f3n de error no comprobada en Apache Tomcat. Si Tomcat est\u00e1 configurado para utilizar un componente ServerAuthContext de autenticaci\u00f3n de Jakarta (anteriormente JASPIC) personalizado que puede generar una excepci\u00f3n durante el proceso de autenticaci\u00f3n sin establecer expl\u00edcitamente un estado HTTP para indicar un error, la autenticaci\u00f3n puede no fallar, lo que permite al usuario omitir el proceso de autenticaci\u00f3n. No se conocen componentes de autenticaci\u00f3n de Jakarta que se comporten de esta manera. Este problema afecta a Apache Tomcat: desde 11.0.0-M1 hasta 11.0.0-M26, desde 10.1.0-M1 hasta 10.1.30, desde 9.0.0-M1 hasta 9.0.95. Se recomienda a los usuarios que actualicen a la versi\u00f3n 11.0.0, 10.1.31 o 9.0.96, que solucionan el problema."}], "lastModified": "2025-01-24T20:15:32.803", "sourceIdentifier": "security@apache.org"}