BeeGFS (beegfs-ctl / metadata server): TENANT ISOLATION: authentication bypass by talking directly to a BeeGFS metadata

Impact

TENANT ISOLATION: authentication bypass by talking directly to a BeeGFS metadata server. BeeGFS is a common choice for AI-training scratch storage because it is fast and easy to stand up, and its threat model assumes the storage network is private. Anyone who reaches the metadata server can act against the filesystem's metadata — which means other tenants' namespaces on a shared BeeGFS deployment.

Who can reach it

Network access to a BeeGFS metadata server. The advisory notes such servers are typically not exposed externally — but inside a GPU cluster, 'not externally exposed' still means reachable by every tenant workload on the storage VLAN.

What to do

Upgrade BeeGFS past 7.1.3 and enable connection authentication (the shared-secret connAuthFile), then restart the metadata, storage and client services — a coordinated restart that stalls I/O, so drain jobs first. Enabling connAuth is the load-bearing step; the version upgrade alone does not help if authentication stays off.

References