AI analysis
Apache DolphinScheduler versions from 3.2.0 before 3.4.3 have a missing authorization check that lets an authenticated non-admin user retrieve Kubernetes configuration data reserved for administrator-managed cluster configuration. The user triggers this through DolphinScheduler while logged in; the returned kubeconfig includes credentials that can be used to authenticate directly to the Kubernetes API outside the product. What an attacker can do depends on those credentials: cluster-admin or broadly privileged service-account access may allow reading Kubernetes Secrets, creating pods, and establishing persistent cluster access. Organizations running an affected release that stores Kubernetes cluster configuration are in scope. No public proof of concept is known, the issue is not in CISA KEV, and CVSS is not yet scored.
What to do: Upgrade Apache DolphinScheduler to 3.4.3, which fixes the missing authorization check. Treat kubeconfigs stored on affected instances as exposed: rotate the associated tokens or certificates, reduce their Kubernetes RBAC to least privilege, and review cluster audit logs for API access that did not originate from DolphinScheduler. Until the upgrade, restrict DolphinScheduler logins to users who require them.
Affected
| Apache DolphinScheduler | 3.2.0 before 3.4.3 |
Estimated exposure
—No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
An authorization vulnerability in Apache DolphinScheduler allows authenticated non-admin users to retrieve Kubernetes configuration data intended for administrator-managed cluster configuration. The exposed kubeconfig data contains credentials that may allow users to authenticate directly to the Kubernetes API outside DolphinScheduler. The impact depends on the permissions granted to the disclosed credentials. If the kubeconfig provides cluster-admin or broadly privileged service-account access, an attacker may read Kubernetes Secrets, create pods, and establish persistent access to the cluster. This issue affects Apache DolphinScheduler: from 3.2.0 before 3.4.3. Users are recommended to upgrade to version 3.4.3, which fixes the issue.