Baremetal Operator
Approved changes feed: RSS · Atom
cpe:2.3:a:linuxfoundation:baremetal_operator:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Linuxfoundation (4b459c90-8cdb-5268-beb4-b69b5fe74234) |
|---|---|
| Product | Baremetal Operator (9d4c4ff8-e51a-5952-9672-de6b2172f95f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/metal3-io/baremetal-operator |
purl2cpe | 2026-06-01 10:13:21.278718 |
pkg:golang/github.com/metal3-io/baremetal-operator |
purl2cpe | 2026-06-01 10:13:21.278719 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-30841 |
vulnerable | 2026-06-08 06:04:41.196074 |
Ironic and ironic-inspector deployed within Baremetal Operator may expose as ConfigMaps
MEDIUM (6)
Baremetal Operator (BMO) is a bare metal host provisioning integration for Kubernetes. Prior to version 0.3.0, ironic and ironic-inspector deployed within Baremetal Operator using the included `deploy.sh` store their `.htpasswd` files as ConfigMaps instead of Secrets. This causes the plain-text username and hashed password to be readable by anyone having a cluster-wide read-access to the management cluster, or access to the management cluster's Etcd storage. This issue is patched in baremetal-operator PR#1241, and is included in BMO release 0.3.0 onwards. As a workaround, users may modify the kustomizations and redeploy the BMO, or recreate the required ConfigMaps as Secrets per instructions in baremetal-operator PR#1241.
Published: 2023-04-26T18:24:04.479Z
Updated: 2025-01-30T21:30:50.655Z |
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.