In Eclipse BaSyx Helm Charts versions 3.0.0-rc.1 to 3.12.1 of the `basyx` chart, deployments with the bundled Keycloak enabled store the passwords of…
In Eclipse BaSyx Helm Charts versions 3.0.0-rc.1 to 3.12.1 of the `basyx` chart, deployments with the bundled Keycloak enabled store the passwords of the Keycloak users that the chart creates in cleartext in a Kubernetes ConfigMap. The template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `<release>-basyx-keycloak-init-config`. By default this includes the bootstrap administrator user. That user holds the `admin` role and has a non-temporary password. A principal that can read ConfigMaps but not Secrets in the release namespace, such as a holder of the built-in Kubernetes `view
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Eclipse Foundation
- Product
- Eclipse BaSyx Helm Charts
- CVSS v3.1
- 7.5 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Fix
- available
- Weakness
- CWE-312, CWE-522
- Exposure class
- Identity, Developer platform, Web platform
- NVD status
- Received
Why it ranks 42 (Notable)
- CVSS v3.1 7.5 high
- Exposed product class: identity
- Fix available
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.