How severe is GHSA-9wh7-397j-722m?

GHSA-9wh7-397j-722m has a CVSS score of 6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9wh7-397j-722m?

GHSA-9wh7-397j-722m affects the following packages: github.com/metal3-io/baremetal-operator (Go). Ecosystems affected: Go.

How do I fix GHSA-9wh7-397j-722m?

Update github.com/metal3-io/baremetal-operator to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9wh7-397j-722m is resolved across your whole dependency graph.

How do I detect GHSA-9wh7-397j-722m in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/metal3-io/baremetal-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9wh7-397j-722m if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-9wh7-397j-722m actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-9wh7-397j-722m, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-9wh7-397j-722m?

GHSA-9wh7-397j-722m has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9wh7-397j-722m?

GHSA-9wh7-397j-722m is classified as Information Exposure (CWE-200), CWE-319 (CWE-319). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9wh7-397j-722m published, and has it been updated?

GHSA-9wh7-397j-722m was published on April 26, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Ironic and ironic-inspector may expose as ConfigMapsGHSA-9wh7-397j-722m

MEDIUMFix: metal3-io/baremetal-operator#1241

GHSA-9wh7-397j-722m is a medium-severity (CVSS 6) Information Exposure vulnerability in github.com/metal3-io/baremetal-operator. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/metal3-io/baremetal-operator — see the affected versions and patch details below.

Also known asCVE-2023-30841

Published

Apr 26, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9wh7-397j-722m.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/metal3-io/baremetal-operator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Patches

This issue is patched in baremetal-operator PR#1241, and is included in BMO release 0.3.0 onwards.

Workarounds

User may modify the kustomizations and redeploy the BMO, or recreate the required ConfigMaps as Secrets per instructions in baremetal-operator PR#1241

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/metal3-io/baremetal-operator`	all versions	0.3.0`go get github.com/metal3-io/baremetal-operator@v0.3.0`

Affected Products

1 product · 1 configurations

Application

baremetal operatorlinuxfoundation

< 0.3.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Baremetal Operator (BMO) is a bare metal host provisioning integration f…

github.comNVDMay 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/metal3-io/baremetal-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/metal3-io/baremetal-operator to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9wh7-397j-722m is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 4.12	`openshift4/topology-aware-lifecycle-manager-operator-bundle:v4.12.8-17`	RHSA-2024:3801
Red Hat OpenShift Container Platform 4.13	`openshift4/ose-baremetal-rhel8-operator:v4.13.0-202305021616.p0.ge037aa0.assembly.stream`	RHSA-2023:1326
Red Hat OpenShift Container Platform 4.14	`openshift4/topology-aware-lifecycle-manager-rhel8-operator:v4.14.0-68`	RHSA-2023:6143

Frequently Asked Questions

### Impact 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. ### Patches This issue is patched in [baremetal-operator PR#1241](https://github.com/metal3-io/baremetal-operator/pull/1241), and is included in BMO release 0.3.0 onwards. ### Workarounds User may modify the kustomizations and redeploy