Secuno
ENNL
Book demo

CVE-2024-37371

Mit Kerberos 5 out-of-bounds read

9.1 CRITICALEPSS 1.86%
  1. Published28 Jun 2024

Description

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected products

Mit Kerberos 5< 1.21.3
Debian Linux11.0 · 12.0

Remediation

Fixed in
Mit Kerberos 5≥ 1.21.3

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1078378.2
RIOT is an open-source microcontroller operating system designed for Internet of Things…
CVE-2026-78269.1
A heap-based out-of-bounds read in the BufferSerializerIOv2_ReadBuffer function…
CVE-2026-823348.1
IBM Guardium Data Protection 12.0, 12.1, 12.2 is vulnerable to a heap-based…
CVE-2026-144968.2
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0…
CVE-2026-764578.6
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-772148.2
libexpat before commit 13c5f63 contains a heap buffer over-read vulnerability in…

Frequently asked

Is CVE-2024-37371 being actively exploited?

CVE-2024-37371 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.86%.

How severe is CVE-2024-37371?

CVE-2024-37371 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 1.86% probability of exploitation.

Which products are affected by CVE-2024-37371?

Affected products include Mit Kerberos 5, Debian Linux.

How do I fix CVE-2024-37371?

Upgrade affected software to a fixed version, for example Mit Kerberos 5 1.21.3 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-37371 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.