CVE-2024-0006: DB User Password Leak in Application Log
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone on the same network segment can trigger it. Administrator privileges are required. Special conditions such as timing or configuration are required.
- Fixed version: YugabyteDB YugabyteDB Anywhere 2.18.9.0, 2.20.2.3, 2024.1.1.0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to YugabyteDB YugabyteDB Anywhere 2.18.9.0, 2.20.2.3, 2024.1.1.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-532
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Yugabyte
- 5.4
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| yugabyte | yugabytedb | cpe:2.3:a:yugabyte:yugabytedb |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Yugabyte). Independent of NVD's CPE analysis and usually ahead of it.
YugabyteDB YugabyteDB Anywhere
- 2.18.0.0 and later · before 2.18.9.0affected · git
- 2.20.0.0 and later · before 2.20.2.3affected · git
- 2024.0.0.0 and later · before 2024.1.1.0affected · git
Same product
yugabytedb: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-6908Admin Can Escalate Privileges to SuperAdmin Using Manual PUT Request24Monitor
- CVE-2024-6895Insecure Account Profile Management24Monitor
- CVE-2024-11165An information disclosure vulnerability exists in the backup configuration process where the SAS token is not masked in the configuration…22Monitor
Published before and after this one in the same product
- Later →CVE-2024-11193Nov 13, 2024 · An information disclosure vulnerability exists in Yugabyte Anywhere, where the LDAP bind password is logged in plaintext within application…20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| YugabyteDB YugabyteDB Anywhere | 2.18.9.0 | Vendor (CNA) |
| YugabyteDB YugabyteDB Anywhere | 2.20.2.3 | Vendor (CNA) |
| YugabyteDB YugabyteDB Anywhere | 2024.1.1.0 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-11165117 days apartAn information disclosure vulnerability exists in the backup configuration process where the SAS token is not masked in the configuration…22Monitor
- CVE-2024-11193117 days apartAn information disclosure vulnerability exists in Yugabyte Anywhere, where the LDAP bind password is logged in plaintext within application…20Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1032 · Jul 22, 2024(Yugabyte Güvenlik Zafiyeti)
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- Administrator privileges are required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- High
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.