QuayApplication · Redhat
CVE-2019-3865
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 · uneditedA vulnerability was found in quay-2, where a stored XSS vulnerability has been found in the super user function of quay. Attackers are able to use the name field of service key to inject scripts and make it run when admin users try to change the name.
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 confidenceA stored XSS vulnerability in Quay-2 container registry's super user function allows attackers to inject malicious scripts into the name field of service keys. When administrators view or modify these service keys, the injected script executes in their browser, potentially allowing session hijacking or actions performed on behalf of the admin.
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
= 2.0.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Quay versionCheck the installed version of Redhat Quay in your environment. This can typically be found in the Quay configuration, package manager, or container image tag. Compare it to the affected version: 2.0.0Affected if The installed Quay version is exactly 2.0.0
-
Identify superuser accessDetermine if your Quay deployment has the superuser function enabled and accessible. Check for admin/superuser accounts or roles that have privileges to manage service keys.Affected if Superuser or admin access to service key management exists in your environment
-
Inspect service key names for XSS payloadsAccess the service key management interface through the superuser function. Review all existing service keys and inspect the name field of each for any suspicious JavaScript tags, event handlers, or encoded payloads that could indicate XSS injection.Affected if Any service key contains a name field with script tags, javascript: URIs, or other XSS-related patterns such as <script, onerror, onload, or similar HTML/JS injection attempts
-
Review browser console for XSS errorsIf you have access, log into Quay as an administrator and navigate to the service key management section. Open browser developer tools and check the console for any XSS-related errors or warnings when viewing or editing service keys.Affected if JavaScript executes unexpectedly or console shows XSS errors when viewing service key names
You are affected if running Quay version 2.0.0 and have service keys with malicious content in the name field that will execute when viewed by administrators in the superuser interface.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of Quay-2 that addresses this vulnerability. As a workaround, carefully validate and sanitize any service key names before modification, and consider restricting access to the super user function until the patch is applied.
Fix this in Quay
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3865 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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