Summary
A critical missing-authentication flaw in SeaweedFS allows unauthenticated clients to invoke filer IAM gRPC operations when the filer signing key is not configured. Any client able to reach the filer gRPC port may create credentials, modify policies, and obtain administrative control of S3-compatible storage.
Affected context
The issue affects SeaweedFS filer deployments using versions before 4.24 when jwt.filer_signing.key is unset. In this configuration, the SeaweedIdentityAccessManagement gRPC service may be exposed without mandatory authentication, making its administrative RPC methods reachable to clients that can connect to the filer gRPC port.
Exploit preconditions
- Attack surface: SeaweedFS filer gRPC service
- Required access: Network connectivity to the filer gRPC port; valid authentication is not required in the vulnerable configuration
- Trigger point: Invocation of IAM RPCs such as user, access-key, or policy management operations
- Why exploitation is possible: The service does not enforce authentication when the filer signing key is absent, allowing unauthorized clients to perform privileged IAM actions
Why this happens
The vulnerability results from registering a security-sensitive gRPC service without requiring authentication under a particular configuration state. This creates an authorization boundary failure mapped to CWE-306: Missing Authentication for Critical Function, because privileged identity and policy operations can be executed before the caller's identity is verified.
Potential impact
- Attackers may create unauthorized users or access keys
- Attackers could alter or replace authorization policies
- Unauthorized clients may gain administrative control of S3-compatible storage
- Stored data may be exposed, modified, deleted, or poisoned
- Compromised credentials may support persistence or lateral movement
General mitigation guidance
Mitigation generally focuses on ensuring that administrative gRPC services fail closed and cannot operate without authenticated callers.
Common defensive patterns include:
- Require signed authentication for all IAM and other privileged filer RPCs
- Treat missing signing keys and incomplete security configuration as startup errors
- Restrict filer gRPC exposure to trusted management networks
- Apply network segmentation and firewall policies that limit reachable administrative ports
- Use least-privilege service identities and narrowly scoped storage policies
- Monitor and rotate administrative credentials and access keys
- Prefer secure-by-default configuration templates that enable authentication
How teams detect issues like this
Organizations can identify this class of issue through:
- Configuration analysis that flags unset authentication or signing-key settings
- Static and architectural checks for privileged gRPC services registered without interceptors or authorization middleware
- Code review signals involving IAM RPCs reachable before caller verification
- Network policy reviews confirming that filer gRPC ports are not broadly reachable
- Audit logging for unexpected user creation, access-key issuance, and policy changes
- Policy enforcement in deployment pipelines requiring authentication for administrative services
Automated security review tools may help detect missing authorization checks and insecure configuration defaults.

