PT-2026-35112 · Go · Github.Com/Oxia-Db/Oxia
Publicado
2026-04-14
·
Atualizado
2026-04-14
CVSS v4.0
9.3
Crítica
| Vetor | AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
Summary
The OIDC authentication provider unconditionally sets
SkipClientIDCheck: true in the go-oidc verifier configuration, disabling the standard audience (aud) claim validation at the library level. This allows tokens issued for unrelated services by the same OIDC issuer to be accepted by Oxia.Impact
In deployments using OIDC authentication, an attacker possessing a valid JWT token issued by the same identity provider but intended for a different service (different
client id/aud) can authenticate to Oxia. This bypasses the intended audience isolation of OAuth2/OIDC.All versions using OIDC authentication are affected.
Details
In
oxiad/common/rpc/auth/oidc.go, both createStaticKeyVerifier() and createRemoteVerifier() set SkipClientIDCheck: true. While a custom audience check exists in Authenticate(), the library-level check — which validates the aud claim against the expected client id — is completely bypassed.Patches
Fixed by removing
SkipClientIDCheck: true and setting the ClientID field from the configured AllowedAudiences.Workarounds
Ensure network-level isolation so that only trusted services can reach the Oxia gRPC endpoints.
Correção
Improper Authentication
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Enumeração de Fraquezas
Identificadores relacionados
Produtos afetados
Github.Com/Oxia-Db/Oxia