CyberRota Analysis
AI-GeneratedCentrifugo's dynamic JWKS endpoint verification prior to version 6.8.1 is vulnerable to key reuse, allowing a key from one issuer to be incorrectly used to verify JWTs from another issuer due to inadequate caching mechanisms. This flaw could lead to unauthorized access or data leakage, posing a significant risk to applications relying on secure token validation. Organizations using Centrifugo should prioritize upgrading to version 6.8.1 to mitigate this high-severity vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Centrifugo is an open-source scalable real-time messaging server. Prior to 6.8.1, Centrifugo dynamic JWKS endpoint verification could reuse a key for one allowed issuer to verify a JWT for another allowed issuer because the JWKS cache and singleflight lookup were keyed only by JWT header kid, not by the resolved JWKS endpoint, issuer, audience, or trust-domain namespace, affecting client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, internal/jwks/cache.go, and internal/jwks/manager.go. This issue is fixed in version 6.8.1.