Mysql K8S Operator
Approved changes feed: RSS · Atom
cpe:2.3:a:canonical:mysql-k8s-operator:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Canonical (bedcba35-8c3d-5a60-8532-2ba876a6ec88) |
|---|---|
| Product | Mysql K8S Operator (07a280e2-1c40-5647-b715-c20724633cb2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-24375 |
vulnerable | 2026-06-08 07:12:48.541468 |
MySQL K8s charm could leak credentials for root-level user `serverconfig`
MEDIUM (5)
Charmed MySQL K8s operator is a Charmed Operator for running MySQL on Kubernetes. Before revision 221, the method for calling a SQL DDL or python based mysql-shell scripts can leak database users credentials. The method mysql-operator calls mysql-shell application rely on writing to a temporary script file containing the full URI, with user and password. The file can be read by a unprivileged user during the operator runtime, due it being created with read permissions (0x644). On other cases, when calling mysql cli, for one specific case when creating the operator users, the DDL contains said users credentials, which can be leak through the same mechanism of a temporary file. All versions prior to revision 221 for kubernetes and revision 338 for machine operators.
Published: 2025-04-09T22:21:37.858Z
Updated: 2025-04-10T15:55:01.617Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.