Yugabyte DB prior 2.18.9.0/2.20.2.3/2024.1.1.0 Application Log log file
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
2.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Yugabyte DB. This vulnerability affects unknown code of the component Application Log Handler. The manipulation leads to log file. This vulnerability was named CVE-2024-0006. The attack needs to be initiated within the local network. There is no exploit available. It is recommended to upgrade the affected component. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as problematic has been found in Yugabyte DB. This affects an unknown part of the component Application Log Handler. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. The summary by CVE is:
Information exposure in the logging system in Yugabyte Platform allows local attackers with access to application logs to obtain database user credentials in log files, potentially leading to unauthorized database access.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-0006 since 11/07/2023. The exploitability is told to be easy. The attack needs to be done within the local network. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 2.18.9.0, 2.20.2.3 or 2024.1.1.0 eliminates this vulnerability. Applying the patch 439c6286f1971f9ac6bff2c7215b454c2025c593 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.3
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: DB 2.18.9.0/2.20.2.3/2024.1.1.0
Patch: 439c6286f1971f9ac6bff2c7215b454c2025c593
Timeline
11/07/2023 CVE reserved07/19/2024 Advisory disclosed
07/19/2024 VulDB entry created
07/22/2024 VulDB entry last update
Sources
Advisory: 439c6286f1971f9ac6bff2c7215b454c2025c593Status: Confirmed
CVE: CVE-2024-0006 (🔒)
GCVE (CVE): GCVE-0-2024-0006
GCVE (VulDB): GCVE-100-271953
Entry
Created: 07/19/2024 07:16 PMUpdated: 07/22/2024 04:25 PM
Changes: 07/19/2024 07:16 PM (69), 07/22/2024 04:25 PM (1)
Complete: 🔍
Cache ID: 18:51E:40
No comments yet. Languages: en.
Please log in to comment.