CVE-2024-24814VulnerabilityPublished 12 Nov 2024Updated 11 Oct 2026

SUSE · security update for mod_auth_openidc

Affects SUSESource GCVE Database

Not known to be exploited : upgrade to 2.4.9.4 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

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

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

Exploitation evidence

Disclosed: evidence found.
CVE published 12 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 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

Upgrade redhat/mod_auth_openidc to 2.4.9.4.

Affected software

Product	Affected	Fixed in
Red Hatredhat/mod_auth_openidc`pkg:rpm/redhat/mod_auth_openidc`Other threats	Affected <2.4.9.4 >=2.3	Fixed in 2.4.9.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released an official security update for mod_auth_openidc to address this vulnerability. Users of affected Red Hat Enterprise Linux 8 versions should apply the update to mod_auth_openidc version 2.4.9.4 or later as provided in Red Hat Advisory RHSA-2024:5289. Detailed update instructions are available at https://access.redhat.com/articles/11258. No additional mitigation steps are required beyond applying the official patch.

Description

A denial of service (DoS) vulnerability (CVE-2024-24814) exists in the mod_auth_openidc Apache HTTP Server module when using the OIDCSessionType client-cookie configuration and manipulating cookies. This vulnerability affects Red Hat Enterprise Linux 8 versions of mod_auth_openidc. Red Hat has released an update to address this issue, which has been rated with moderate security impact. The vulnerability allows an attacker to cause a DoS condition by manipulating cookies. No known exploits in the wild have been reported.

Impact

The vulnerability allows an attacker to cause a denial of service by manipulating cookies when the mod_auth_openidc module is configured with OIDCSessionType client-cookie. This can disrupt the availability of the Apache HTTP Server using this module. There are no reports of active exploitation in the wild. The impact is limited to service disruption and does not include code execution or data breach based on the advisory.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (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 11 Oct 2026, 22:29 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats