Remote Code Execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| YugabyteDB | YugabyteDB | unaffected |
|
Configuration 1 [-]
| AND |
|
No data.
No data available yet.
Vendor Solution
Use Yugabyte version 2.3.3.0-b106 or higher.
Vendor Workaround
In yugaware/config/configs folder there is a file acceptableKeys.yaml which contains a list of acceptable keys for different types of providers. Edit it and restart the Yugaware process to reload the list.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-12615 | 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 Abuse. This vulnerability is associated with program files backup.Py. This issue affects Yugabyte DB: Lesser then 2.2.0.0 |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.776% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.yugabyte.com/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|