# CVE-2019-3864: Cross-site request forgery in quay

> Attackers can exploit static CSRF tokens in Quay to perform actions on behalf of authenticated users, leading to account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rq69-788x-22hh

## What is CVE-2019-3864?

CVE-2019-3864 is a medium-severity vulnerability in Red Hat quay, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-3864?

It affects 1 product.


Products: Redhat Quay.

## How do I fix CVE-2019-3864?

No fix has been published for CVE-2019-3864 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3864 being exploited?

There is no known exploitation of CVE-2019-3864 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat quay

- [CVE-2020-27832](https://insights.sbomify.com/CVE-2020-27832/): Cross-site scripting in quay (critical 9.0)
- [CVE-2025-4374](https://insights.sbomify.com/CVE-2025-4374/): Quay: incorrect privilege assignment (medium 6.5)
- [CVE-2023-4956](https://insights.sbomify.com/CVE-2023-4956/): Quay: clickjacking on config-editor page severity (medium 6.5)
- [CVE-2023-4959](https://insights.sbomify.com/CVE-2023-4959/): Quay: cross-site request forgery (csrf) on config-editor page (medium 6.5)
- [CVE-2019-10205](https://insights.sbomify.com/CVE-2019-10205/): Information disclosure in quay (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3864 and fix it if it is affected.

What it is: CVE-2019-3864 is a medium-severity vulnerability in Red Hat quay, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-3864 in the wild and no public exploit code.

Affected product: Red Hat quay. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-3864/ (Markdown: https://insights.sbomify.com/CVE-2019-3864/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3864
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3864
- OSV: https://osv.dev/vulnerability/CVE-2019-3864

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3864/
Summaries are generated and may contain mistakes; the official description above is the record.