NetSight
mittel4.0

CVE-2023-30840

On a compromised node, the fluid-csi service account can be used to modify node specs

Auswirkung

### Impact If a malicious user gains control of a Kubernetes node running fluid csi pod (controlled by the `csi-nodeplugin-fluid` node-daemonset), he/she can leverage the fluid-csi service account to modify specs of all the nodes in the cluster. However, since this service account lacks "list node" permissions, the attacker may need to use other techniques to identify vulnerable nodes. Once the attacker identifies and modifies the node specs, he/she can manipulate system-level-privileged components to access all secrets in the cluster or execute pods on other nodes. This allows he/she to elevate privileges beyond the compromised node and potentially gain full privileged access to the whole cluster. To exploit this vulnerability, the attacker can make all other nodes unschedulable (for example, patch node with taints) and wait for system-critical components with high privilege to appear on the compromised node. However, this attack requires two prerequisites: a compromised node and identifying all vulnerable nodes through other means. Additionally, since the attack is passive and requires patience and luck, the severity of this finding is considered medium. ### Patches For users who're using version < 0.8.6, >= 0.7.0, upgrade to v0.8.6. ### Workarounds Delete the `csi-nodeplugin-fluid` daemonset in `fluid-system` namespace and avoid using CSI mode to mount FUSE file systems. Alternatively using sidecar mode to mount FUSE file systems is recommended. Refer to [the doc](https://github.com/fluid-cloudnative/fluid/blob/master/docs/en/samples/knative.md) to get a full example of how to use sidecar mode. ### References Fixed by [Fix rbacs and limit CSI Plugin's node related access](https://github.com/fluid-cloudnative/fluid/commit/77c8110a3d1ec077ae2bce6bd88d296505db1550) ### Credits Special thanks to the discoverers of this issue: Nanzi Yang ([nzyang@stu.xidian.edu.cn](mailto:nzyang@stu.xidian.edu.cn))

Ein Angreifer kann die Lücke mit lokalem Zugriff auf das System ausnutzen, mit einem Administratorkonto, allerdings muss ein Nutzer etwas tun, etwa eine Datei oder einen Link öffnen. Dafür müssen bestimmte Bedingungen erfüllt sein, was einen Angriff erschwert. Bei Erfolg: hohes Risiko, dass Daten ausgelesen werden.

Betroffene Pakete

ÖkosystemPaketBetroffenBehoben in
gogithub.com/fluid-cloudnative/fluid>= 0.7.0, < 0.8.60.8.6

Betroffene Produkte · Linuxfoundation

ProduktBetroffene Versionen
Fluid
ab 0.7.0 vor 0.8.6

Schwachstellenklasse

Referenzen