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-1394: Missing Release of Memory after Effective Lifetime in Red Hat Red Hat Ansible Automation Platform 2.4 for RHEL 8

0
High
VulnerabilityCVE-2024-1394cvecve-2024-1394
Published: Thu Mar 21 2024 (03/21/2024, 12:16:38 UTC)
Source: CVE
Vendor/Project: Red Hat
Product: Red Hat Ansible Automation Platform 2.4 for RHEL 8

Description

A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them.

AI-Powered Analysis

AILast updated: 11/13/2025, 23:17:12 UTC

Technical Analysis

CVE-2024-1394 is a vulnerability identified in the Red Hat Ansible Automation Platform 2.4 running on RHEL 8, stemming from a memory leak in the RSA encryption/decryption code implemented in Golang. Specifically, the issue lies in the handling of memory objects 'pkey' and 'ctx' within the function located at github.com/golang-fips/openssl/openssl/rsa.go#L113. The function uses named return parameters and a deferred cleanup function intended to free these objects if an error occurs during context initialization or property setting. However, all error-related return statements follow a pattern ('return nil, nil, fail(...)') that results in 'pkey' and 'ctx' being nil when the deferred cleanup runs, preventing proper memory release. This leads to a memory leak that can be triggered by attacker-controlled inputs, causing resource exhaustion on the affected system. The vulnerability does not impact confidentiality or integrity but severely affects availability by enabling denial of service conditions. It can be exploited remotely without requiring authentication or user interaction. Although no known exploits are currently reported in the wild, the vulnerability has a CVSS 3.1 score of 7.5, indicating high severity. The flaw affects automation platforms critical for IT orchestration, making it a significant risk for enterprise environments relying on Red Hat Ansible Automation Platform 2.4 on RHEL 8.

Potential Impact

The primary impact of CVE-2024-1394 is on system availability due to potential resource exhaustion from memory leaks. For European organizations, especially those using Red Hat Ansible Automation Platform 2.4 on RHEL 8 for automating IT workflows, this vulnerability could lead to denial of service conditions, disrupting critical automation tasks and operational continuity. The absence of confidentiality or integrity impact means data breaches or manipulation are unlikely; however, operational disruptions can cause significant business impact, including downtime, delayed deployments, and increased operational costs. Large-scale or heavily automated environments are particularly vulnerable as repeated exploitation can rapidly consume system memory. Additionally, the vulnerability can be exploited remotely without authentication or user interaction, increasing the risk of widespread disruption. Organizations in sectors with high reliance on automation platforms, such as finance, telecommunications, and manufacturing, may face amplified operational risks.

Mitigation Recommendations

1. Monitor Red Hat and Golang project advisories closely and apply official patches or updates for Red Hat Ansible Automation Platform 2.4 and underlying Golang libraries as soon as they become available. 2. Implement resource usage monitoring and alerting specifically for memory consumption on systems running the affected platform to detect abnormal increases indicative of exploitation attempts. 3. Employ network-level protections such as rate limiting and traffic filtering to reduce exposure to potentially malicious inputs targeting the RSA encryption functions. 4. Isolate critical automation infrastructure within segmented network zones to limit the blast radius of potential denial of service attacks. 5. Conduct regular vulnerability assessments and penetration testing focusing on automation platforms to identify and remediate memory leak or resource exhaustion issues proactively. 6. Consider temporary workarounds such as restarting affected services periodically to release leaked memory until patches are applied. 7. Educate system administrators and DevOps teams about the vulnerability and encourage prompt incident response readiness.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
redhat
Date Reserved
2024-02-09T06:02:35.056Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9816c4522896dcbd66f4

Added to database: 5/21/2025, 9:08:38 AM

Last enriched: 11/13/2025, 11:17:12 PM

Last updated: 11/30/2025, 8:40:24 PM

Views: 36

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.