mirror registry for Red Hat OpenShift: Plaintext Storage of a Password
CVE-2024-3622 is a high-severity plaintext storage of a password vulnerability in mirror registry for Red Hat OpenShift from Red Hat, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.52% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of mirror registry for Red Hat OpenShift you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on access.redhat.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | mirror registry for Red Hat OpenShift | Not specified in the record | Not stated |
| Red Hat | Mirror Registry | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (redhat.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Plaintext Storage of a Password
The product stores a password in plaintext within resources such as memory or files.
How developers prevent this class of flaw
- Avoid storing passwords in easily accessible locations.
- Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
- A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.
More Plaintext Storage of a Password vulnerabilities (CWE-256)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in mirror registry for Red Hat OpenShift
- 8.8 High severity
- 8.2 High severity
- 7.3 High severity
- 7.3 High severity
Recent Plaintext Storage of a Password vulnerabilities
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.