Research

SeaweedFS

Unauthenticated S3 gRPC identity management enables IAM admin access

CriticalPublished

GHSA-5fx4-c9qp-36jc lets an unauthenticated network peer inject a SeaweedFS S3 administrator identity over gRPC.

Affected
SeaweedFS 4.45 and earlier
Attack requirements
Unauthenticated network access to the S3 gRPC port on a deployment without a configured grpc.s3 TLS section

Impact

An unauthenticated network peer can add an administrator identity with chosen credentials to the IAM store. Those credentials are immediately accepted by the normal SigV4 S3 interface and provide administrative access to buckets, objects, and identities.

Technical detail

  • The PutIdentity and RemoveIdentity gRPC handlers forward requests directly to the IAM store without authenticating or authorizing the caller.
  • The service was intended for credential propagation from a filer to S3 servers, but the listener did not enforce that trust boundary.
  • An attacker can inject an identity with Admin actions and then use its access and secret keys through the regular S3 API.

Remediation

  • Block untrusted access to the S3 gRPC port at the network boundary.
  • Configure the grpc.s3 TLS section rather than exposing the default plaintext listener.
  • Follow the upstream security advisory when selecting an updated SeaweedFS release.