High severity · published Jan 21, 2020
CVE-2019-3864
A vulnerability was discovered in all quay-2 versions before quay-3.0.0, in the Quay web GUI where POST requests include a specific parameter which is used as a CSRF token
8.8
CVSS
0.4%
EPSS
No
On KEV
Description
A vulnerability was discovered in all quay-2 versions before quay-3.0.0, in the Quay web GUI where POST requests include a specific parameter which is used as a CSRF token. The token is not refreshed for every request or when a user logged out and in again. An attacker could use a leaked token to gain access to the system using the user's account.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 38% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
QU
Quay · Redhat
before 3.0.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-3864
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-3864
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3864
More from Quay
9.8
CVE-2021-3762
A directory traversal vulnerability was found in the ClairCore engine of Clair
9.0
CVE-2020-27832
A flaw was found in Red Hat Quay, where it has a persistent Cross-site Scripting (XSS) vulnerability when displaying a repository's notification
8.8
CVE-2026-32590
Mirror-registry: remote code execution using pickle deserialization
8.8
CVE-2022-1227
A privilege escalation flaw was found in Podman
8.2
CVE-2026-74243
Quay: unauthenticated secscan notification endpoint in quay when psk is unset