CVE-2024-7923VulnerabilityPublished 4 Sep 2024Updated 11 Nov 2025

CVE-2024-7923: Improper Authentication

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score

9.8Critical

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 4 Sep 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 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-7923, organizations should take the following specific actions: 1) Upgrade Gunicorn to version 22.0 or later to address the underlying issue with header handling. 2) Apply any available patches or updates from Red Hat for Satellite and Pulpcore components as soon as they are released. 3) Review and modify Apache mod_proxy configurations to ensure headers with underscores are properly sanitized or blocked, potentially by disabling or restricting the use of such headers. 4) Implement network segmentation and restrict access to Satellite servers to trusted management networks only, minimizing exposure to untrusted sources. 5) Monitor logs for unusual or malformed HTTP headers that could indicate exploitation attempts. 6) Employ Web Application Firewalls (WAFs) or reverse proxies capable of detecting and blocking malformed headers or suspicious authentication bypass attempts. 7) Conduct thorough audits of Satellite administrative accounts and credentials to detect any unauthorized access. 8) Prepare incident response plans specific to Satellite compromise scenarios to enable rapid containment and recovery.

Description

An authentication bypass vulnerability has been identified in Pulpcore when deployed with Gunicorn versions prior to 22.0, due to the puppet-pulpcore configuration. This issue arises from Apache's mod_proxy not properly unsetting headers because of restrictions on underscores in HTTP headers, allowing authentication through a malformed header. This flaw impacts all active Satellite deployments (6.13, 6.14 and 6.15) which are using Pulpcore version 3.0+ and could potentially enable unauthorized users to gain administrative access.

Impact

The impact of CVE-2024-7923 is severe for organizations using Red Hat Satellite versions 6.13 through 6.15 with Pulpcore 3.0+ deployed behind Apache mod_proxy and Gunicorn versions prior to 22.0. Unauthorized administrative access can lead to full compromise of the Satellite server, allowing attackers to manipulate software repositories, deploy malicious content, disrupt patch management, and potentially pivot to other internal systems. This undermines the integrity and availability of critical infrastructure management processes and can result in widespread operational disruption. Confidential data managed by Satellite, including system inventories and configuration data, may also be exposed or altered. Given Satellite's role in enterprise environments, this vulnerability poses a significant risk to IT supply chain security and compliance. The ease of exploitation without authentication or user interaction increases the likelihood of targeted attacks, especially in environments where Satellite is exposed to untrusted networks or insufficiently segmented.

References

Community reviews

Loading reviews…