First published: Mon Sep 30 2024(Updated: )
Binaries built with golang-1.21.13-3.el9_4 and golang-1.21.13-2.module+el8.10.0+22329+6cd5c9c6 may intermittently return a zeroed buffer from (*boringHMAC).Sum() in FIPS mode due to an uninitialized buffer length variable in the CGO bindings. This bug occurs randomly based on the stack layout at the time of the function call. It is not vulnerable to eg. buffer overflow attack because the underlying openssl routine checks the bounds of the buffer before writing to it. However, it may 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 is able to 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.
Affected Software | Affected Version | How to fix |
---|---|---|
Go (Golang) language by Google |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-2315719 is considered a moderate severity vulnerability as it can lead to insecure handling of cryptographic operations.
To address REDHAT-BUG-2315719, you should update to the latest version of golang that includes the appropriate patches.
The impact of REDHAT-BUG-2315719 includes the risk of returning a zeroed buffer from cryptographic functions, potentially compromising data integrity.
REDHAT-BUG-2315719 affects binaries built with golang-1.21.13-3.el9_4 and golang-1.21.13-2.module+el8.10.0+22329+6cd5c9c6.
Yes, REDHAT-BUG-2315719 occurs intermittently based on the stack layout at the time, particularly in FIPS mode.