dbcve.org
ClusternetApplication

CVE-2023-30622

HIGH · 8.8 CVSS v3.1 Published 2023-04-24
Fix available
A fix is available. Upgrade to after 0.15.1 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Clusternet is a general-purpose system for controlling Kubernetes clusters across different environments. An issue in clusternet prior to version 0.15.2 can be leveraged to lead to a cluster-level privilege escalation. The clusternet has a deployment called `cluster-hub` inside the `clusternet-system` Kubernetes namespace, which runs on worker nodes randomly. The deployment has a service account called `clusternet-hub`, which has a cluster role called `clusternet:hub` via cluster role binding. The `clusternet:hub` cluster role has `"*" verbs of "*.*"` resources. Thus, if a malicious user can access the worker node which runs the clusternet, they can leverage the service account to do malicious actions to critical system resources. For example, the malicious user can leverage the service account to get ALL secrets in the entire cluster, resulting in cluster-level privilege escalation. Version 0.15.2 contains a fix for this issue.

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 · high confidence

Clusternet versions prior to 0.15.2 contain a cluster-level privilege escalation where the clusternet-hub service account (running on worker nodes) is bound to a cluster-admin equivalent role (clusternet:hub with '*' verbs on '*.*' resources). An attacker with worker node access can abuse this service account to access all secrets across the entire cluster.

MitigationUpgrade clusternet to version 0.15.2 or later, which contains the fix for this issue. Alternatively, restrict the clusternet:hub cluster role permissions to follow least-privilege principles.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ClusternetApplication
Affected:<= 0.15.1

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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. Check if Clusternet is installed
    Run 'kubectl get namespaces' and look for clusternet-related namespaces such as clusternet-system, or run 'kubectl get pods -A | grep clusternet' to find clusternet pods.
    Affected if No clusternet pods or namespaces are found.
  2. Identify the clusternet-hub version
    Run 'kubectl get deployment -n clusternet-system' to find the clusternet-hub deployment, then check the image tag with 'kubectl get deployment clusternet-hub -n clusternet-system -o jsonpath="{.spec.template.spec.containers[0].image}"'. Compare the version number to 0.15.1.
    Affected if The installed version is 0.15.1 or earlier.
  3. Inspect the clusternet:hub cluster role
    Run 'kubectl get clusterrole clusternet:hub -o yaml' and examine the rules section. Look for a rule with resources set to ['*.*'] or ['*'] and verbs set to ['*'].
    Affected if The clusternet:hub cluster role grants '*' verbs on '*.*' or '*' resources.
  4. Check for cluster role binding to clusternet-hub service account
    Run 'kubectl get clusterrolebinding | grep clusternet:hub' to find cluster role bindings associated with the clusternet:hub role. Then verify the subject is the clusternet-hub service account in the clusternet-system namespace.
    Affected if A cluster role binding exists linking the clusternet-hub service account to the clusternet:hub cluster role.

A user is affected if clusternet version 0.15.1 or earlier is installed AND the clusternet:hub cluster role grants '*' verbs on '*.*' or '*' resources, which allows the clusternet-hub service account to access all secrets cluster-wide.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.15.1
Interim mitigation

Upgrade clusternet to version 0.15.2 or later, which contains the fix for this issue. Alternatively, restrict the clusternet:hub cluster role permissions to follow least-privilege principles.

Recommended fix High confidence

0.15.2

  1. Upgrade Clusternet from any version <= 0.15.1 to version 0.15.2 or later
  2. Verify the upgrade by checking the clusternet-system namespace for the running cluster-hub deployment
  3. Confirm the clusternet-hub service account permissions have been restricted from the overly permissive cluster role

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clusternet Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30622 — 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-2023-30622 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