CVE-2024-5891
MEDIUMDescription
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.
Is your site exposed to CVE-2024-5891?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
Weakness Type (CWE)
Affected Products
| Vendor | Product |
|---|---|
| redhat | quay |
References
Frequently Asked Questions
What is CVE-2024-5891? +
How severe is CVE-2024-5891? +
What products are affected by CVE-2024-5891? +
How do I check if I'm vulnerable to CVE-2024-5891? +
Related Vulnerabilities
An improper validation of credentials vulnerability in the CommvaultSecurityIQ integration for Cortex XSOAR and Cortex XSIAM allows an unauthenticated attacker …
A security issue exists within DataMosaix™ Private Cloud, allowing attackers to bypass MFA during setup and obtain a valid login-token …
A security issue exists within FactoryTalk® Services Platform (FTSP), allowing an attacker to bypass JWT signature validation during Okta Web …
Doorkeeper is an OAuth 2 provider for Ruby on Rails. In version 1.9.0, an attacker who knows only a dynamically …
This vulnerability exists in the CAP back office application due to improper authentication check at the API endpoint. An unauthenticated …
The affected Ebyte product's vendor configuration utility permits access to administrative functions without verifying the operator's identity under certain credential …