CVE-2024-3622 json
Mirror-registry: plain-text default csrf secret key
published 2024-04-25 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-32201
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
A flaw was found when using mirror-registry to install Quay. It uses a default secret, which is stored in plain-text format in one of the configuration template files. This issue may lead to all instances of Quay deployed using mirror-registry to have the same secret key. This flaw allows a malicious actor to craft session cookies and as a consequence, it may lead to gaining access to the affected Quay instance.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-3622 updated cvss 8.8
mirror-registry: Plain-text default CSRF secret key
-
Red Hat mirror registry for Red Hat OpenShift mirror-registry-containeraffected: no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Red Hat mirror registry for Red Hat OpenShift
Classification
- Weakness
-
- CWE-256 Plaintext Storage of a Password
References
-
access.redhat.com
/security/cve/CVE-2024-3622
vdb-entry, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2274400
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2024-3622
- NVD CVE-2024-3622
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.