CVE-2024-37370: In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a con...
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.
Security readout for executives and security teams
Plain-English summary
This flaw affects MIT Kerberos 5 before 1.21.3. A network attacker could alter an unprotected field in a protected GSS Kerberos message so the receiving application sees the message as shorter than it really is. Business risk depends on where Kerberos GSS protected communications are used.
Executive priority
Treat as a high-priority patching item for environments that rely on Kerberos-secured service communication. The urgency is highest where MIT krb5 is embedded in externally reachable, cross-domain, or vendor-managed systems. No active exploitation is evidenced in the supplied sources.
Technical view
CVE-2024-37370 is a CWE-345 issue in krb5 GSS wrap token handling. The plaintext Extra Count field of a confidential GSS krb5 wrap token can be modified, causing the unwrap result to appear truncated to the application. The CVSS vector is network, low complexity, no privileges, no user interaction, confidentiality high.
Likely exposure
Organizations are most likely exposed through servers, clients, appliances, or embedded products using MIT krb5 versions before 1.21.3 for GSSAPI-protected Kerberos communications. The bundle lists NetApp and Siemens advisories, suggesting downstream vendor assessment is relevant, but affected products are not enumerated here.
Exploitation context
The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is remotely reachable under the CVSS assessment and requires no privileges or user interaction, but exposure depends on applications using confidential GSS krb5 wrap tokens.
Researcher notes
The key research question is whether an application’s protocol semantics become unsafe when a confidential GSS krb5 wrapped token is delivered as truncated plaintext. Validate exposure by implementation and version, not by the generic affected CPE data, which is incomplete in the supplied bundle.
Mitigation direction
Upgrade MIT Kerberos 5 krb5 to version 1.21.3 or later where directly managed.
Review MIT advisory and the referenced upstream fix for authoritative remediation details.
Check NetApp and Siemens advisories for product-specific updates or mitigations.
Prioritize internet-facing or cross-trust Kerberos GSSAPI services first.
If no direct package update exists, obtain guidance from the affected vendor.
Validation and detection
Inventory systems and products that include MIT Kerberos 5 or krb5 libraries.
Confirm krb5 package versions and flag versions earlier than 1.21.3.
Identify applications using Kerberos GSSAPI confidentiality or wrap tokens.
Check vendor advisories for matching product names, versions, and fixed releases.
Verify patched hosts are using the updated krb5 libraries after restart or redeploy.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-345 · source CWE mapping
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.