CVE-2024-0006

Database credential disclosure via discarded redaction context

Published Jul 19, 2024 · Updated Aug 1, 2024

Sensitive-data logging in YugabyteDB Anywhere 2.18.0.0 through 2.18.8.0 allows local users to read database credentials. NodeUniverseManager.executeNodeAction replaces the shell context's existing redaction values instead of merging them, so YSQL and YCQL passwords reach application.log without masking. Access to the host's application logs is required, and exposed credentials allow unauthorized database access.

CVSS severity5.4
Medium
EPSS probability0.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive-data logging in YugabyteDB Anywhere 2.18.0.0 through 2.18.8.0 allows local users to read database credentials. NodeUniverseManager.executeNodeAction replaces the shell context's existing redaction values instead of merging them, so YSQL and YCQL passwords reach application.log without masking. Access to the host's application logs is required, and exposed credentials allow unauthorized database access.

The record

CVE
CVE-2024-0006
Published
Jul 19, 2024
Updated
Aug 1, 2024
Vendor
YugabyteDB, Inc.
Product
YugabyteDB
Classifications
CWE-532, CAPEC-560, T1552.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 19, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 1, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2024.0.0.0 <2024.1.1.0
  2. Affected versionversion=2.18.0.0 <2.18.9.0
  3. Affected versionversion=2.20.0.0 <2.20.2.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

YugabyteDB, Inc. · YugabyteDBversion=2024.0.0.0 <2024.1.1.0; version=2.18.0.0 <2.18.9.0; version=2.20.0.0 <2.20.2.3
YugabyteDB, Inc. · YugabyteDB Anywhereversion=2024.0.0.0 <2024.1.1.0; version=2.18.0.0 <2.18.9.0; version=2.20.0.0 <2.20.2.3

Published CVSS scores

5.4Yugabyte, Inc.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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-532Insertion of Sensitive Information into Log File
CAPEC-560Use of Known Domain Credentials
T1552.001Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo