Skip to content

Vendor

YugabyteDB Inc vulnerabilities

17 published CVES affecting YugabyteDB Inc, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
17
Critical
3
High
4
Medium
9
Low
1
Unscored
0
CISA KEV
0
Atom feed of YugabyteDB Inc alerts

Products

Latest YugabyteDB Inc CVEs

Newest publication first

  1. MediumCVSS 5.1 EPSS 0.26%

    YugabyteDB Anywhere web server does not properly enforce authentication for the /metamaster/universe API endpoint. An unauthenticated attacker could exploit this flaw to obtain server networking configuration details, including private and public IP addresses and DNS records.

  2. MediumCVSS 4.1 EPSS 0.19%

    The YugabyteDB tablet server contains a flaw in its YCQL query handling that can trigger a null pointer dereference when processing certain malformed inputs. An authenticated attacker could exploit this issue to crash the YCQL tablet server, resulting in a denial of service.

  3. HighCVSS 7.0 EPSS 0.40%

    YugabyteDB has been collecting diagnostics information from YugabyteDB servers, which may include sensitive gflag configurations. To mitigate this, we recommend upgrading the database to a version where this information is properly redacted.

  4. MediumCVSS 5.0 EPSS 0.32%

    An information disclosure vulnerability exists in Yugabyte Anywhere, where the LDAP bind password is logged in plaintext within application logs. This flaw results in the unintentional exposure of sensitive information in Yugabyte Anywhere logs, potentially allowing unauthorized...

  5. MediumCVSS 5.7 EPSS 0.14%

    An information disclosure vulnerability exists in the backup configuration process where the SAS token is not masked in the configuration response. This oversight results in sensitive information leakage within the yb_backup log files, exposing the SAS token in plaintext. The lea...

  6. MediumCVSS 6.1 EPSS 0.24%

    Insufficient authentication in user account management in Yugabyte Platform allows local network attackers with a compromised user session to change critical security information without re-authentication. An attacker with user session and access to application can modify setting...

  7. MediumCVSS 5.4 EPSS 0.27%

    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.

  8. CVE-2023-6002 Log Injection

    Published
    MediumCVSS 6.1 EPSS 0.48%

    YugabyteDB is vulnerable to cross site scripting (XSS) via log injection. Writing invalidated user input to log files can allow an unprivileged attacker to forge log entries or inject malicious content into the logs.

  9. HighCVSS 7.5 EPSS 0.39%

    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 Yug...

  10. CriticalCVSS 9.8 EPSS 0.78%

    External Control of Critical State Data, Improper Control of Generation of Code ('Code Injection') vulnerability in YugaByte, Inc. Yugabyte DB on Windows, Linux, MacOS, iOS (DevopsBase.Java:execCommand, TableManager.Java:runCommand modules) allows API Manipulation, Privilege Abus...

  11. CriticalCVSS 9.8 EPSS 0.51%

    The High Availability functionality of Yugabyte Anywhere can be abused to write arbitrary files through the backup upload endpoint by using path traversal characters. This vulnerability is associated with program files PlatformReplicationManager.Java. This issue affects YugabyteD...

  12. CriticalCVSS 9.8 EPSS 0.64%

    Server-Side Request Forgery (SSRF), Improperly Controlled Modification of Dynamically-Determined Object Attributes, Improper Restriction of Excessive Authentication Attempts vulnerability in YugaByte, Inc. Yugabyte Managed allows Accessing Functionality Not Properly Constrained b...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.