CVE-2023-30512
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 · uneditedCubeFS through 3.2.1 allows Kubernetes cluster-level privilege escalation. This occurs because DaemonSet has cfs-csi-cluster-role and can thus list all secrets, including the admin secret.
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 confidenceCubeFS through 3.2.1 contains a Kubernetes RBAC misconfiguration where the DaemonSet is assigned the cfs-csi-cluster-role with excessive privileges, allowing it to list all secrets cluster-wide including administrative credentials. This enables a cluster-level privilege escalation from a component that should have limited permissions.
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<= 3.2.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify CubeFS DaemonSet deploymentRun `kubectl get daemonset -A -o wide` and look for daemonsets with 'cfs' or 'cubefs' in the name, or check your namespace if CubeFS is installed in a dedicated namespaceAffected if A CubeFS DaemonSet is present in the cluster
-
Check CubeFS versionRun `kubectl get daemonset -n <namespace> <daemonset-name> -o jsonpath='{.spec.template.spec.containers[0].image}'` to get the image, then extract the version tagAffected if The version is 3.2.1 or earlier (any version through 3.2.1)
-
Verify cfs-csi-cluster-role existsRun `kubectl get clusterrole cfs-csi-cluster-role -o yaml` to retrieve the role definitionAffected if The clusterrole with this exact name exists in the cluster
-
Inspect secrets permissions in the roleIn the clusterrole output, check the 'rules' section for 'resources: [secrets]' and 'verbs' including 'list' or 'get' with no namespace restriction (empty 'apiGroups' or '*')Affected if The role grants list or get permissions on secrets at cluster scope (no namespace limitation)
-
Confirm role binding to DaemonSet service accountRun `kubectl get clusterrolebinding -A | grep cfs-csi` to find the binding, then check `kubectl get clusterrolebinding <binding-name> -o yaml` to verify it binds cfs-csi-cluster-role to the DaemonSet's service accountAffected if The cfs-csi-cluster-role is bound to a service account used by the CubeFS DaemonSet
You are affected if CubeFS version 3.2.1 or earlier is deployed AND the cfs-csi-cluster-role grants cluster-wide list or get permissions on secrets to the DaemonSet service account.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict the cfs-csi-cluster-role to follow the principle of least privilege by removing the ability to list all secrets, and grant only the minimum permissions required for the DaemonSet to function. Upgrade to a patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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