YugabyteDB

YugabyteDB v2.21.1.0 was discovered to contain a buffer overflow via the "insert into" parameter.

External Control of Critical State Data, Improper Control of Generation of Code ('Code Injection') vulnerability in YugaByte, Inc.

An issue was discovered in the YugabyteDB 2.6.1 when using LDAP-based authentication in YCQL with Microsoft’s Active Directory.

The High Availability functionality of Yugabyte Anywhere can be abused to write arbitrary files through the backup upload endpoint by using path traversal characters.

Server-Side Request Forgery (SSRF), Improperly Controlled Modification of Dynamically-Determined Object Attributes, Improper Restriction of Excessive Authentication Attempts vulnerability in YugaByte, Inc.

Prometheus metrics are available without authentication.

The controller responsible for setting the logging level does not include any authorization checks to ensure the user is authenticated.

CF CLI version prior to v6.45.0 (bosh release version 1.16.0) writes the client id and secret to its config file when the user authenticates with --client-credentials flag.

YugabyteDB is vulnerable to cross site scripting (XSS) via log injection.

YugabyteDB has been collecting diagnostics information from YugabyteDB servers, which may include sensitive gflag configurations.

YugabyteDB diagnostic information was transmitted over HTTP, which could expose sensitive data during transmission

Shared Access Signature token is not masked in the backup configuration response and is also exposed in the yb_backup logs

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.

Improper privilege management in Yugabyte Platform allows authenticated admin users to escalate privileges to SuperAdmin via a crafted PUT HTTP request, potentially leading to unauthorized access to sensitive system func…

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…

An information disclosure vulnerability exists in the backup configuration process where the SAS token is not masked in the configuration response.

YugabyteDB Anywhere web server does not properly enforce authentication for the /metamaster/universe API endpoint.

An information disclosure vulnerability exists in Yugabyte Anywhere, where the LDAP bind password is logged in plaintext within application logs.

The YugabyteDB tablet server contains a flaw in its YCQL query handling that can trigger a null pointer dereference when processing certain malformed inputs.

YugabyteDB Anywhere displays LDAP bind passwords configured via gflags in cleartext within the web UI.