dbcve.org
YugabytedbApplication · Yugabyte

CVE-2023-4640

HIGH · 7.5 CVSS v3.1 Published 2023-08-30
Fix available
A fix is available. Upgrade to after 2.17.3.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
The controller responsible for setting the logging level does not include any authorization checks to ensure the user is authenticated. This can be seen by noting that it extends Controller rather than AuthenticatedController and includes no further checks. This issue affects YugabyteDB Anywhere: from 2.0.0 through 2.17.3

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 logging level controller in YugabyteDB Anywhere extends the base Controller class instead of AuthenticatedController and lacks any authorization checks. This allows unauthenticated remote attackers to modify logging levels by directly accessing the endpoint, affecting versions 2.0.0 through 2.17.3.

MitigationModify the controller to extend AuthenticatedController or implement explicit authentication validation to ensure only authenticated users can modify logging settings.

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.17.3.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 if YugabyteDB Anywhere is installed
    Look for YugabyteDB processes running (ps aux | grep yugabyte) or check for installation directories such as /opt/yugabyte or /usr/local/yugabyte
    Affected if YugabyteDB Anywhere process or installation found
  2. Determine the installed YugabyteDB Anywhere version
    Run 'yb_version.sh' or check /opt/yugabyte/etc/VERSION file, or use the UI: Help > About in the YugabyteDB Anywhere web console
    Affected if Version falls within 2.0.0 through 2.17.3.0 inclusive
  3. Verify the logging endpoint is accessible
    Check if port 7000 (default YugabyteDB Anywhere UI port) is open and accessible from the network using nmap or curl to the /api/v1/logging endpoint
    Affected if Port 7000 is exposed and the /api/v1/logging endpoint responds without authentication
  4. Confirm lack of authentication on logging endpoint
    Attempt a curl request to http://<host>:7000/api/v1/logging/level without providing any authentication credentials
    Affected if The endpoint returns a successful response (200 OK) without requiring authentication

If YugabyteDB Anywhere version is between 2.0.0 and 2.17.3.0 and the logging endpoint on port 7000 is accessible without credentials, the environment is affected by CVE-2023-4640.

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 a release after 2.17.3.0
Interim mitigation

Modify the controller to extend AuthenticatedController or implement explicit authentication validation to ensure only authenticated users can modify logging settings.

Recommended fix Moderate confidence

Version newer than 2.17.3.0 (refer to official YugabyteDB security bulletins for exact fixed release)

  1. Check the official YugabyteDB security advisories or release notes for CVE-2023-4640 to confirm the exact fixed version
  2. Upgrade YugabyteDB Anywhere to a version newer than 2.17.3.0 that includes the fix for this improper access control vulnerability
  3. After upgrade, verify that the logging level controller now properly extends AuthenticatedController and requires authentication

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

Fix this in Yugabytedb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4640 — 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-4640 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