Centrifugo
Centrifugo: Client-forgeable headers emulation lets any client spoof headers forwarded to proxy backends
Centrifugo is an open-source scalable real-time messaging server. Prior to 6.9.0, Centrifugo copies the client-controlled protocol.ConnectRequest.headers map through OnClientConnecting in internal/client/handler.go, ConnectEvent.Headers, and SetEmulatedHeadersToContext. The requestHeaders path in internal/proxy/http.go, the requestMetadata path in internal/proxy/grpc.go, and the Consume path in internal/unigrpc/grpc.go can forward an allowlisted value as a trusted backend header or metadata value. A remote client can spoof a header such as x-trusted-user for connect, refresh, subscribe, publish, RPC, and related proxy calls when the backend relies on that header for authentication or authorization. The unidirectional gRPC transport has no transport-level HTTP header that can override the emulated value. This issue is fixed in version 6.9.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 6.9.0
Fixed in 6.9.0
Mitigation
Upgrade centrifugo to 6.9.0 or later.
References
- Vendor advisory github.com/centrifugal/centrifugo/security/adv…
- Patch github.com/centrifugal/centrifugo/pull/1182
- Patch github.com/centrifugal/centrifugo/commit/84d38…
1 more
- Release notes github.com/centrifugal/centrifugo/releases/tag…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.