AWS efs-utils cross-filesystem read and write in mount port selection
AWS amazon-efs-utils · aws-efs-csi-driver
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| AWS amazon-efs-utils |
| No fix yet |
| AWS aws-efs-csi-driver |
| No fix yet |
| AWS aws-efs-csi-driver |
| No fix yet |
Original description
A time-of-check time-of-use (TOCTOU) race condition in the local port selection in AWS efs-utils (amazon-efs-utils) before 3.3.5 might allow a user that can start EFS mounts on a shared host to read and write a different Amazon EFS or S3 Files file system that is mounted on that same host, under that mount's IAM identity and access point, via concurrent mount operations. Only file systems mounted on the same host at the same time can be affected. Every mount involved was configured by the owner of that host, using credentials and access points that owner controls, against file systems whose owners had already granted that host access, so the issue grants no access beyond what the host was already permitted and does not cross AWS account boundaries unless the host's owner configured a cross-account mount. The practical risk is lateral access between workloads on the same host at the same time, for example one container reading another container's file system under that container's identity. The issue does not expose the other mount's IAM credentials or TLS session keys.