VulnerabilityPublished 12 Jun 2024Updated 2 Aug 2024

CVE-2024-5891: Red Hat Quay 3 · Weak Authentication

Affects Red Hat Quay 3Source CVE Database V5

Not known to be exploited · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.2Medium

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

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

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

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

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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

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

AI-suggested

Immediately review and update OAuth client ID management practices to ensure client IDs are not exposed or easily obtainable by unauthorized parties.
Enforce strict authorization checks on all endpoints and applications, ensuring that authentication alone does not grant access. Implement role-based access control (RBAC) or attribute-based access control (ABAC) mechanisms.
Apply the latest patches and updates from Red Hat as they become available to address this vulnerability directly.
Audit existing applications and services integrated with Red Hat Quay 3 to verify that they do not rely solely on authentication for access control.
Monitor logs and authentication events for unusual OAuth token usage or authentication attempts from unexpected client IDs.
Consider implementing additional layers of security such as network segmentation and multi-factor authentication (MFA) where applicable.
Educate development and operations teams about the distinction between authentication and authorization to prevent similar misconfigurations.

Description

A vulnerability was found in Quay. If an attacker can obtain the client ID for an application, they can use an OAuth token to authenticate despite not having access to the organization from which the application was created. This issue is limited to authentication and not authorization. However, in configurations where endpoints rely only on authentication, a user may authenticate to applications they otherwise have no access to.

Impact

The primary impact of CVE-2024-5891 is unauthorized authentication to applications within Red Hat Quay 3 environments. While the vulnerability does not directly grant authorization, it can lead to unauthorized access if applications rely solely on authentication for access control. This can result in exposure of sensitive container images, metadata, or internal services to unauthorized users. Organizations using Red Hat Quay 3 in their container supply chain or DevOps pipelines may face risks of data leakage or unauthorized manipulation of container images. The impact is limited to confidentiality and integrity, with no direct availability impact. However, the potential for unauthorized access could facilitate further attacks or lateral movement within an environment. Since Red Hat Quay is widely used in enterprise container management, organizations with containerized workloads and DevOps practices are at risk. The medium severity score reflects the need for attention but indicates that exploitation requires specific conditions and is not trivial.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 02:54 UTC

Technical details

References

Community reviews

Related threats