dbcve.org
QuayApplication · Redhat

CVE-2024-9683

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Quay's authentication mechanism allows successful login with only a truncated portion of a user's password. The password verification process truncates passwords before comparison, meaning an attacker who obtains or guesses only the first ~73 characters of a password can authenticate. This weakens password policy enforcement and reduces the effective entropy of passwords.

MitigationUpgrade Quay to the version that fixes password truncation in the authentication verification. Ensure passwords are compared in full without server-side truncation. Consider implementing additional authentication controls as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QuayApplication
Affected:= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Quay installation version
    Run 'quay version' or check the Quay container/image version. If using operator-based deployment, check the operator version or the Quay custom resource. Alternatively, query the Quay API endpoint /api/v1/whoami or check the UI footer for version information.
    Affected if The installed version is Red Hat Quay 3.0.0 exactly, or if the version falls within the affected range and password authentication is in use.
  2. Verify password-based authentication is enabled
    Check the Quay configuration file (config.yaml) or the UI Authentication settings. Look for authentication providers that use username/password login. This includes local database authentication or LDAP bind authentication.
    Affected if Password-based authentication is the configured method for user login.
  3. Check password policy configuration
    Examine the Quay config.yaml for any password policy settings under AUTHENTICATION or similar sections. Look for settings like minimum password length, password complexity rules, or any truncation-related configuration.
    Affected if Password policies are defined but may be bypassed due to truncation at ~73 characters.
  4. Review authentication logs for truncation behavior
    Examine Quay authentication logs for any patterns related to password verification. While direct truncation evidence may not be logged, check for successful logins that follow unexpected patterns or repeated login attempts.
    Affected if Password authentication attempts succeed with passwords shorter than what the organization's policy specifies.

A user is affected if they are running Red Hat Quay version 3.0.0 with password-based authentication enabled, where the password verification truncates input at approximately 73 characters before comparison.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Quay to the version that fixes password truncation in the authentication verification. Ensure passwords are compared in full without server-side truncation. Consider implementing additional authentication controls as defense-in-depth.

Fix this in Quay Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9683 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data