quay mirror-registry Redis Password cleartext storage in file

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

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.

Detailsinfo

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.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB 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.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Cleartext storage in file
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/10/2024 🔍
04/11/2024 +1 days 🔍
04/11/2024 +0 days 🔍
05/16/2024 +35 days 🔍

Sourcesinfo

Advisory: bugzilla.redhat.com
Status: Not defined

CVE: CVE-2024-3625 (🔍)
GCVE (CVE): GCVE-0-2024-3625
GCVE (VulDB): GCVE-100-260385

Entryinfo

Created: 04/11/2024 09:49
Updated: 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.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!