Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-9355: Use of Uninitialized Variable

0
Medium
VulnerabilityCVE-2024-9355cvecve-2024-9355
Published: Tue Oct 01 2024 (10/01/2024, 18:17:29 UTC)
Source: CVE

Description

A vulnerability was found in Golang FIPS OpenSSL. This flaw allows a malicious user to randomly cause an uninitialized buffer length variable with a zeroed buffer to be returned in FIPS mode. It may also be possible to force a false positive match between non-equal hashes when comparing a trusted computed hmac sum to an untrusted input sum if an attacker can send a zeroed buffer in place of a pre-computed sum.  It is also possible to force a derived key to be all zeros instead of an unpredictable value.  This may have follow-on implications for the Go TLS stack.

AI-Powered Analysis

AILast updated: 10/04/2025, 11:20:39 UTC

Technical Analysis

CVE-2024-9355 is a medium-severity vulnerability identified in the Golang FIPS OpenSSL implementation. The flaw arises from the use of an uninitialized buffer length variable in FIPS mode, which can lead to the return of a zeroed buffer length instead of a properly initialized value. This vulnerability can be exploited by a malicious actor to cause incorrect cryptographic operations, including forcing a false positive match between non-equal hashes during HMAC sum comparisons. Specifically, an attacker who can supply a zeroed buffer in place of a pre-computed HMAC sum may trick the system into accepting invalid authentication codes. Additionally, the vulnerability can cause a derived cryptographic key to be all zeros rather than a securely generated unpredictable value. Such weaknesses undermine the integrity and confidentiality guarantees provided by cryptographic functions and may have cascading effects on the Go TLS stack, potentially compromising secure communications. The vulnerability requires local access (AV:L) with high attack complexity (AC:H) and low privileges (PR:L), but no user interaction (UI:N). The scope is unchanged (S:U), and the impact on confidentiality and integrity is high, with a low impact on availability. No known exploits are currently reported in the wild, and no specific affected versions or patches have been detailed yet.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the security of applications and services relying on Golang's FIPS OpenSSL cryptographic libraries, especially those implementing TLS for secure communications. The potential for false positive HMAC matches and zeroed derived keys can lead to unauthorized access, data tampering, or interception of sensitive information. Critical sectors such as finance, healthcare, government, and telecommunications that depend on strong cryptographic assurances could face data breaches or regulatory non-compliance if exploited. The flaw could also undermine trust in digital signatures and authentication mechanisms, impacting secure transactions and communications. Given the medium CVSS score and the requirement for local access, the threat is more relevant in environments where attackers can gain some level of system access, such as multi-tenant cloud services or compromised internal networks. The cascading impact on the Go TLS stack could affect a broad range of Go-based applications widely used in Europe, increasing the potential attack surface.

Mitigation Recommendations

European organizations should proactively audit their use of Golang FIPS OpenSSL libraries and monitor for updates or patches addressing CVE-2024-9355. Until patches are available, organizations should restrict local access to systems running vulnerable versions, enforce strict privilege separation, and implement robust monitoring for anomalous cryptographic operations or authentication failures. Code reviews and testing should focus on cryptographic key derivation and HMAC verification routines to detect unexpected zeroed buffers or mismatches. Where feasible, consider temporarily disabling FIPS mode or using alternative cryptographic libraries with verified security until a fix is applied. Additionally, organizations should enhance network segmentation and endpoint security controls to limit the ability of attackers to gain local access. Incident response plans should be updated to include detection and remediation steps for cryptographic anomalies related to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
redhat
Date Reserved
2024-09-30T17:07:30.833Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682cd0fb1484d88663aec8e1

Added to database: 5/20/2025, 6:59:07 PM

Last enriched: 10/4/2025, 11:20:39 AM

Last updated: 10/16/2025, 4:54:14 AM

Views: 23

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats