How severe is CVE-2024-45054?

CVE-2024-45054 has a CVSS score of 2.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-45054?

CVE-2024-45054 affects the following packages: github.com/hwameistor/hwameistor (Go). Ecosystems affected: Go.

How do I fix CVE-2024-45054?

Update github.com/hwameistor/hwameistor to 0.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45054 is resolved across your whole dependency graph.

How do I detect CVE-2024-45054 in my Go dependencies?

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

How do I mitigate CVE-2024-45054 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2024-45054 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-45054 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-45054?

CVE-2024-45054 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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 CVE-2024-45054?

CVE-2024-45054 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-45054 published, and has it been updated?

CVE-2024-45054 was published on August 28, 2024 and was last updated on October 28, 2026. 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

LOW severity

CVE-2024-45054 — hwameistor

LOWFix: hwameistor/hwameistor@edf4ceb

CVE-2024-45054 is a low-severity (CVSS 2.8) Information Exposure vulnerability in github.com/hwameistor/hwameistor. A fix is available for github.com/hwameistor/hwameistor — see the affected versions and patch details below.

Potential Permission Leakage of Cluster Level in hwameistor

Also known asGHSA-mgwr-h7mv-fh29GO-2024-3103

Published

Aug 28, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 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 CVE-2024-45054.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% 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/hwameistor/hwameistor

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

What kind of vulnerability is it? Who is impacted? This ClusterRole has * verbs of * resources. If a malicious user can access the worker node which has hwameistor's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation.

Patches

Has the problem been patched? What versions should users upgrade to?

= v0.14.6

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? Update and Limit the ClusterRole using security-role.

References

Are there any links users can visit to find out more? issues: https://github.com/hwameistor/hwameistor/issues/1457 https://github.com/hwameistor/hwameistor/issues/1460

also reported by users via mails: sparkEchooo, younaman

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hwameistor/hwameistor`	all versions	0.14.6`go get github.com/hwameistor/hwameistor@v0.14.6`

Affected Products

1 product · 1 configurations

Application

hwameistorhwameistor

< 0.14.6

range

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/hwameistor/hwameistor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hwameistor/hwameistor to 0.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45054 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ This ClusterRole has * verbs of * resources. If a malicious user can access the worker node which has hwameistor's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation. ### Patches _Has the problem been patched? What versions should users upgrade to?_ >= v0.14.6 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Update and Limit the ClusterRole using [security-role](https://gith