quay mirror-registry Redis Password cleartext storage in file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in quay mirror-registry. This issue affects some unknown processing of the component Redis Password Handler. Performing a manipulation results in cleartext storage in file. This vulnerability is known as CVE-2024-3625. No exploit is available.
Details
A vulnerability was found in quay mirror-registry (version now known). It has been classified as problematic. This affects some unknown processing of the component Redis Password Handler. The manipulation with an unknown input leads to a cleartext storage in file vulnerability. CWE is classifying the issue as CWE-313. The product stores sensitive information in cleartext in a file, or on disk. This is going to have an impact on confidentiality.
The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2024-3625 since 04/10/2024. The exploitability is told to be easy. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.3
CNA Vector (Red Hat, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storage in fileCWE: CWE-313 / CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/10/2024 🔍04/11/2024 🔍
04/11/2024 🔍
05/16/2024 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2024-3625 (🔍)
GCVE (CVE): GCVE-0-2024-3625
GCVE (VulDB): GCVE-100-260385
Entry
Created: 04/11/2024 09:49Updated: 05/16/2024 15:42
Changes: 04/11/2024 09:49 (49), 05/16/2024 15:37 (1), 05/16/2024 15:42 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.