dbcve.org
YugabytedbApplication · Yugabyte

CVE-2023-6001

HIGH · 7.5 CVSS v3.1 Published 2023-11-08
Fix available
A fix is available. Upgrade to 2.18.4.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Prometheus metrics are available without authentication. These expose detailed and sensitive information about the YugabyteDB Anywhere environment.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Prometheus metrics endpoint in YugabyteDB Anywhere is accessible without authentication, allowing attackers to retrieve sensitive operational details about the database environment including internal architecture, query patterns, and potentially secrets exposed in metric labels.

MitigationEnable authentication on the Prometheus metrics endpoint and restrict network access to authorized monitoring systems only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
YugabytedbApplication
Affected:>= 2.0.0, < 2.18.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed YugabyteDB version
    Run 'yb_server --version' or check the package version installed via your package manager (yum, apt, etc.)
    Affected if Installed version is 2.0.0 or higher but below 2.18.4.0
  2. Locate Prometheus metrics endpoint configuration
    Search for 'prometheus' in YugabyteDB configuration files (typically in /etc/yugabyte/ or paths specified during installation). Check for entries containing 'prometheus' or 'metrics' endpoint paths.
    Affected if Configuration files contain Prometheus metrics endpoint settings without authentication requirements
  3. Verify metrics endpoint network binding
    Check if the Prometheus metrics port (default 7000 or 7001) is listening on a non-localhost interface by running 'netstat -tlnp | grep -E "700[01]"' or 'ss -tlnp | grep -E "700[01]"'
    Affected if The metrics port binds to 0.0.0.0 or an external IP rather than 127.0.0.1 only
  4. Test unauthenticated access to metrics endpoint
    Attempt to curl the metrics endpoint: 'curl http://<server>:7000/metrics' or 'curl http://<server>:7001/metrics' (adjust port based on your configuration)
    Affected if The request returns metric data without requiring authentication credentials
  5. Confirm authentication is not enforced
    Review YugabyteDB Anywhere UI settings under 'Metrics' or 'Monitoring' configuration, or check yb-master and yb-tserver flags for 'prometheus' authentication-related settings
    Affected if No authentication mechanism (such as basic auth or TLS client certs) is configured for the Prometheus endpoint

A user is affected if their YugabyteDB version falls within 2.0.0 to 2.18.4.0 and the Prometheus metrics endpoint responds without requiring authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.18.4.0 or later
Fixed in 2.18.4.0
Interim mitigation

Enable authentication on the Prometheus metrics endpoint and restrict network access to authorized monitoring systems only.

Recommended fix High confidence

2.18.4.0 or later

  1. 1. Review YugabyteDB upgrade documentation and ensure compatibility with your current environment
  2. 2. Create a full backup of your current YugabyteDB database
  3. 3. Test the upgrade in a non-production environment first
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Upgrade YugabyteDB to version 2.18.4.0 or later
  6. 6. After upgrade, verify that Prometheus metrics endpoint now requires authentication
  7. 7. Update any monitoring tools or scripts that access Prometheus metrics to use proper authentication credentials
Caveat Review release notes for any breaking changes between your current version and 2.18.4.0; plan for potential application compatibility testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yugabytedb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6001 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data