dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2024-36534

HIGH · 8.4 CVSS v3.1 Published 2024-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insecure permissions in hwameistor v0.14.3 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Insecure permissions in hwameistor v0.14.3 allow attackers to access sensitive data and escalate privileges by obtaining the service account's token. This indicates a likely RBAC misconfiguration or improper access control on service account credentials, enabling unauthorized access to the service account's identity and associated permissions.

MitigationReview and restrict RBAC policies to implement least-privilege access for service accounts, ensure service account tokens are not exposed or accessible to untrusted principals, and consider upgrading to a patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify hwameistor version
    Run 'helm list' or check the hwameistor operator deployment to determine the installed version. If using kubectl, run: kubectl get deployment -n hwameistor -o jsonpath='{.items[*].spec.template.spec.containers[*].image}'
    Affected if The installed version is v0.14.3 exactly, or falls within the v0.14.3 release line without having applied patches
  2. Review RBAC ClusterRoleBindings
    List all ClusterRoleBindings associated with hwameistor service accounts: kubectl get clusterrolebindings -o jsonpath='{.items[?(@.subjects[?(@.kind=="ServiceAccount")])}' | jq -r '.[] | select(.roleRef.name | contains("hwameistor"))'
    Affected if ClusterRoleBindings grant excessive permissions (such as cluster-admin or wildcarded verbs like '*' on resources) to hwameistor service accounts
  3. Inspect service account token secrets
    List secrets of type 'kubernetes.io/service-account-token' in the hwameistor namespace: kubectl get secrets -n hwameistor -o jsonpath='{.items[?(@.type=="kubernetes.io/service-account-token")]}'
    Affected if Service account tokens exist and are accessible to users or groups beyond the minimal required set of administrators
  4. Check RoleBindings for privilege escalation paths
    Examine RoleBindings in all namespaces for bindings that allow untrusted users to access hwameistor-related service accounts: kubectl get rolebindings --all-namespaces -o json | jq -r '.items[] | select(.subjects[].kind=="User" or .subjects[].kind=="Group") | select(.roleRef.name | contains("hwameistor"))'
    Affected if Users or groups outside the security team have bindings that could allow them to impersonate hwameistor service accounts
  5. Verify service account impersonation permissions
    Check if any ClusterRole grants 'impersonate' permissions on service accounts: kubectl get clusterroles -o json | jq -r '.items[] | select(.rules[]?.verbs[]=="impersonate") | .metadata.name'
    Affected if Non-admin ClusterRoles or Roles contain 'impersonate' verbs on serviceaccounts resources, allowing unauthorized identity escalation

A user is affected if running hwameistor v0.14.3 with overly permissive RBAC that allows untrusted principals to access service account tokens or impersonate service accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and restrict RBAC policies to implement least-privilege access for service accounts, ensure service account tokens are not exposed or accessible to untrusted principals, and consider upgrading to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36534 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data