Yugabyte
Products by Yugabyte Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 0 vulnerabilities in Yugabyte . Last year Yugabyte had 5 security vulnerabilities published. Right now, Yugabyte is on track to have less security vulnerabilities in 2024 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 5 | 8.14 |
| 2022 | 1 | 9.80 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 7.80 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Yugabyte vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Yugabyte Security Vulnerabilities
YugabyteDB is vulnerable to cross site scripting (XSS) via log injection
CVE-2023-6002
6.1 - Medium
- November 08, 2023
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.
XSS
Prometheus metrics are available without
authentication
CVE-2023-6001
7.5 - High
- November 08, 2023
Prometheus metrics are available without authentication. These expose detailed and sensitive information about the YugabyteDB Anywhere environment.
AuthZ
The controller responsible for setting the logging level does not include any authorization
checks to ensure the user is authenticated
CVE-2023-4640
7.5 - High
- August 30, 2023
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
The High Availability functionality of Yugabyte Anywhere
CVE-2023-0745
9.8 - Critical
- February 09, 2023
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 YugabyteDB Anywhere: from 2.0.0.0 through 2.13.0.0
Directory traversal
Server-Side Request Forgery (SSRF)
CVE-2023-0574
9.8 - Critical
- February 09, 2023
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 by ACLs, Communication Channel Manipulation, Authentication Abuse.This issue affects Yugabyte Managed: from 2.0.0.0 through 2.13.0.0
An issue was discovered in the YugabyteDB 2.6.1 when using LDAP-based authentication in YCQL with Microsofts Active Directory
CVE-2022-37397
9.8 - Critical
- August 12, 2022
An issue was discovered in the YugabyteDB 2.6.1 when using LDAP-based authentication in YCQL with Microsofts Active Directory. When anonymous or unauthenticated LDAP binding is enabled, it allows bypass of authentication with an empty password.
authentification
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
CVE-2019-3800
7.8 - High
- August 05, 2019
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. A local authenticated malicious user with access to the CF CLI config file can act as that client, who is the owner of the leaked credentials.
Information Disclosure