Is CVE-2024-37371 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-37371 being exploited in the wild.

How severe is CVE-2024-37371?

Critical severity, with a CVSS score of 9.1, published 28 June 2024.

Which products and versions are affected?

Mit Kerberos 5 1.3 to 1.21.2; Siemens S7-1500 CPU 1518-4 PN/DP MFP >= V3.1.5.

Is there a fix for CVE-2024-37371?

A patch was published on 2024-06-28: Fixed in krb5 version 1.21.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2024-37371 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2024-37371?

Check whether you run Mit Kerberos 5 or Siemens S7-1500 CPU 1518-4 PN/DP MFP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-37371: MIT Kerberos 5 out-of-bounds read in GSS message token handling

CVE-2024-37371 · Severity: critical · CVSS 9.1 · Published 2024-06-28

MIT Kerberos 5, a widely used authentication protocol for securing network communications, contains a vulnerability in how it handles security tokens. An unauthenticated attacker can send specially crafted messages to trigger memory errors, potentially leading to the exposure of sensitive information or causing a system crash. This impact can extend to various enterprise systems and industrial hardware, such as Siemens SIMATIC controllers, that rely on this library for secure access.

Technologies: Mit Kerberos 5. Vendors: Mit, Siemens.

Quick answers

Is CVE-2024-37371 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-37371 being exploited in the wild.
How severe is CVE-2024-37371?: Critical severity, with a CVSS score of 9.1, published 28 June 2024.
Which products and versions are affected?: Mit Kerberos 5 1.3 to 1.21.2; Siemens S7-1500 CPU 1518-4 PN/DP MFP >= V3.1.5.
Is there a fix for CVE-2024-37371?: A patch was published on 2024-06-28: Fixed in krb5 version 1.21.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2024-37371 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2024-37371?: Check whether you run Mit Kerberos 5 or Siemens S7-1500 CPU 1518-4 PN/DP MFP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An out-of-bounds read vulnerability (CWE-125) exists in MIT Kerberos 5 (krb5) within the GSS-API message token handling logic. The flaw is triggered when the library processes message tokens with invalid length fields, specifically within functions like gss_krb5int_unseal_token_v3() and kg_unseal_iov_token(). A remote, unauthenticated attacker can exploit this by sending malformed tokens over the network. Successful exploitation can result in unauthorized access to sensitive memory contents or a denial-of-service (DoS) condition via a crash. The vulnerability was introduced in version 1.3 and is fixed in version 1.21.3.

Affected products

MIT Kerberos 5 (krb5) 1.3 to 1.21.2
Siemens S7-1500 CPU 1518-4 PN/DP MFP >= V3.1.5

Timeline

2024-06-28: disclosed
2024-06-28: advisory
2024-06-28: patched: Fixed in krb5 version 1.21.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.