Red Hat Quay 3 Truncated Password Version authentication bypass

Summaryinfo

A vulnerability marked as critical has been reported in Red Hat Quay 3. Affected by this vulnerability is an unknown functionality of the component Truncated Password Version Handler. This manipulation causes authentication bypass. This vulnerability appears as CVE-2024-9683. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Red Hat Quay 3. It has been declared as critical. Affected by this vulnerability is an unknown code of the component Truncated Password Version Handler. The manipulation with an unknown input leads to a authentication bypass vulnerability. The CWE definition for the vulnerability is CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A vulnerability was found in Quay, which allows successful authentication even when a truncated password version is provided. This flaw affects the authentication mechanism, reducing the overall security of password enforcement.  While the risk is relatively low due to the typical length of the passwords used (73 characters), this vulnerability can still be exploited to reduce the complexity of brute-force or password-guessing attacks. The truncation of passwords weakens the overall authentication process, thereby reducing the effectiveness of password policies and potentially increasing the risk of unauthorized access in the future.

The advisory is shared at access.redhat.com. This vulnerability is known as CVE-2024-9683 since 10/09/2024. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/24/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-50089). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Red Hat

Name

• Quay

Version

• 3

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion