CVE-2024-12698VulnerabilityPublished 18 Dec 2024Updated 20 Nov 2025

CVE-2024-12698: Uncontrolled Resource Consumption

Source CVE Database V5

Mentioned vulnerabilities

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 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 2026-10-25.

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 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

AI-suggested

To mitigate CVE-2024-12698, organizations should: 1) Monitor vendor advisories closely and apply complete patches or updates as soon as they become available to address the incomplete fix. 2) Implement strict access controls to limit authenticated user privileges, minimizing the number of users who can create streams in the affected component. 3) Enforce resource quotas and limits on containers and pods running the ose-olm-catalogd-container to prevent excessive resource consumption. 4) Use runtime monitoring and alerting tools to detect abnormal resource usage patterns indicative of exploitation attempts. 5) Conduct regular audits of authentication and authorization configurations to ensure no unnecessary privileges are granted. 6) Consider network segmentation and isolation of critical container management components to reduce exposure. 7) Prepare incident response plans to quickly respond to potential denial of service events related to this vulnerability. These measures go beyond generic advice by focusing on controlling authenticated user capabilities and resource management specific to container orchestration environments.

Description

An incomplete fix for ose-olm-catalogd-container was issued for the Rapid Reset Vulnerability (CVE-2023-39325/CVE-2023-44487) where only unauthenticated streams were protected, not streams created by authenticated sources.

Impact

The primary impact of CVE-2024-12698 is denial of service through resource exhaustion, which can disrupt the availability of the ose-olm-catalogd-container and potentially the broader OpenShift Operator Lifecycle Manager functionality. This disruption can impair the deployment, upgrade, and management of Kubernetes operators, affecting application lifecycle management in containerized environments. Organizations relying heavily on OpenShift and OLM for critical workloads may experience service outages or degraded performance, impacting business continuity. Since the vulnerability requires authenticated access, insider threats or compromised credentials could be leveraged to exploit this flaw. The lack of impact on confidentiality and integrity limits data breach risks, but availability degradation can still cause operational and financial damage. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once patches are released. The medium severity rating suggests a moderate but actionable risk that should be addressed promptly to maintain system stability and reliability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 11:49 UTC

Technical details

References

Community reviews

Related threats