CVE-2024-24789VulnerabilityPublished 13 Nov 2024Updated 13 Oct 2026

Red Hat Security Advisory: ACS 4.4 enhancement update

Affects Red Hat ACS 4.4Source GCVE Database

Mentioned vulnerabilities

Not known to be exploited : upgrade Red Hat ACS 4.4 to 4.4.6 soon.

Data as of 26 Oct 2026, 10:12 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.4.6

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Red Hat ACS 4.4 to 4.4.6.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=4.4.0 <4.4.6 Red Hat Red Hat Advanced Cluster Security for Kubernetes RHACS 4.4 for RHEL 8 s390x advanced-cluster-security/rhacs-central-db-rhel8@sha256:ee6981dd3ba39a27922af01c8b4daadbefe669bf749323c2f6c1b338130d51ca_s390x Red Hat OpenShift Serverless Red Hat OpenShift Serverless 1.0 src openshift-serverless-clients-0:1.12.0-10.el8.src	Fixed in 4.4.6

AI-suggested

Red Hat has released RHACS 4.4.6 which includes fixes for all listed vulnerabilities and a bug fix for image scan result display. Users running RHACS versions >=4.4.0 and <4.4.6 should upgrade to version 4.4.6 promptly to mitigate these security issues. No additional mitigation steps are indicated beyond applying this official patch release.

Description

This release of RHACS 4.4.6 introduces the following changes: Bug fix: * Fixed an issue where you could not view detailed scan results for certain images in RHACS because the page redirected to an error after a brief display. (ROX-24326) Security fixes: * encoding/gob: golang: Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion (CVE-2024-34156) * body-parser: Denial of Service Vulnerability in body-parser (CVE-2024-45590) * dompurify: DOMPurify vulnerable to tampering by prototype pollution (CVE-2024-48910) * golang: archive/zip: Incorrect handling of certain ZIP files (CVE-2024-24789) * golang: net/netip: Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses (CVE-2024-24790) For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities fixed in RHACS 4.4.6 could lead to denial of service conditions (e.g., panic due to stack exhaustion, body-parser DoS), unexpected behavior in IP address handling, and potential tampering via prototype pollution. These issues may affect the stability and security of the RHACS environment, potentially impacting cluster security operations. The severity is rated as Important/High by Red Hat, reflecting significant but not critical impact. No active exploitation has been reported.

Summary

The RHACS 4.4.6 release addresses several security vulnerabilities: CVE-2024-24789 involves incorrect handling of certain ZIP files in golang's archive/zip package; CVE-2024-24790 concerns unexpected behavior in golang's net/netip Is methods for IPv4-mapped IPv6 addresses; CVE-2024-34156 is a panic caused by stack exhaustion when decoding deeply nested structures in encoding/gob; CVE-2024-45590 is a denial of service vulnerability in body-parser; and CVE-2024-48910 involves prototype pollution tampering in DOMPurify. These issues were fixed in the updated RHACS 4.4.6 images. The advisory recommends upgrading from versions >=4.4.0 and <4.4.6 to 4.4.6. No known exploits in the wild have been reported.

CWE-20Improper Input Validation (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #18OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Attack Surface Reduction
Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of…
Architecture and Design · Libraries or Frameworks
Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-115Misinterpretation of Input (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-405Asymmetric Resource Consumption (Amplification) (opens in a new tab)
Class weakness
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
Architecture and Design
An application must make resources available to a client commensurate with the client's access level.
Architecture and Design
An application must, at all times, keep track of allocated resources and meter their usage appropriately.
System Configuration
Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1321Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (opens in a new tab)
Variant weakness
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
Implementation
By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
Architecture and Design
By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
Implementation · Input Validation
When handling untrusted objects, validating using a schema can be used.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Aug 2026, 17:55 UTC

WeaknessesCWE-20, CWE-115, CWE-674 +2

Technical details

References

Community reviews

Related threats