# CVE-2019-3867: Missing authorization in quay

> Attackers with stolen session tokens can control or delete user container repositories because Quay sessions never expire.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pf92-7x8p-6x5m

## What is CVE-2019-3867?

CVE-2019-3867 is a medium-severity missing authorization vulnerability in quay, published on 18 Mar 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in the Quay web application. Sessions in the Quay web application never expire. An attacker, able to gain access to a session, could use it to control or delete a user's container repository. Red Hat Quay 2 and 3 are vulnerable to this issue.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Redhat Quay.

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

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

## Is CVE-2019-3867 being exploited?

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

## Other vulnerabilities in 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-3867 and fix it if it is affected.

What it is: CVE-2019-3867 is a medium-severity missing authorization vulnerability in quay, published on 18 Mar 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-3867 in the wild and no public exploit code.

Affected product: 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-3867/ (Markdown: https://insights.sbomify.com/CVE-2019-3867/index.md)
```

## Sources

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

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