Hwameistor Potential Permission Leakage of Cluster Level
CVE-2024-45054GHSA-mgwr-h7mv-fh29
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/hwameistor/hwameistor 0.14.6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/hwameistor/hwameistor
- Affected
- <= 0.14.5
- Fixed in
- 0.14.6
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-mgwr-h7mv-fh29 lists affected ranges: Go github.com/hwameistor/hwameistor >=0 <=0.14.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 4.6 · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2024-45054: 0.25% estimated exploitation activity in the next 30 days; percentile 16.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-mgwr-h7mv-fh29
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-45054 Advisory: Hwameistor Potential Permission Leakage of Cluster Level IDs: CVE-2024-45054, GHSA-mgwr-h7mv-fh29 Record: https://patchnext.com/advisories/cve-2024-45054 (revision 1, source checked 26 Oct 2026, 15:08 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/hwameistor/hwameistor 0.14.6. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/hwameistor/hwameistor: affected <= 0.14.5; fixed in 0.14.6 ## Suggested inspection (read-only) - Go github.com/hwameistor/hwameistor: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/hwameistor/hwameistor. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-mgwr-h7mv-fh29 (GitHub-reviewed advisory GHSA-mgwr-h7mv-fh29 lists affected ranges: Go github.com/hwameistor/hwameistor >=0 <=0.14.5) Commands are suggestions: review each one before running it.
Loading voting…