CVE-2024-37370
HighSummary
In MIT Kerberos 5 before version 1.21.3, an attacker can modify the Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.
Risk Assessment
Modification of the token may lead to unauthorized access or incorrect data processing by the application, posing a serious security threat.
Recommendation
It is recommended to upgrade to version 1.21.3 or later to mitigate this vulnerability.
Other vulnerabilities in MIT Kerberos 5
See all- CVE-2024-37371Critical
In MIT Kerberos 5 before version 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
- CVE-2026-40356Medium
In MIT Kerberos 5 (krb5) before 1.22.3, an integer underflow and resultant out-of-bounds read occur if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.
- CVE-2026-40355Medium
In MIT Kerberos 5 (krb5) before version 1.22.3, there is a NULL pointer dereference when an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.
- CVE-2025-3576Medium
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes.
Original NVD description (English source)
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.