Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets
tink-crypto tink-go
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tink-crypto tink-go |
| No fix yet |
Original description
Tink-go (tink-crypto/tink-go) through 2.8.0 contains an input-validation vulnerability where keyset.NewHandleWithNoSecrets() and ReadWithNoSecrets() skip the structural Validate() step before constructing a keyset.Handle, allowing malformed public or no-secret keysets that violate Tink's keyset invariants to be accepted. Attackers can supply a malformed keyset, such as one with an enabled public key lacking a valid primary key or a DESTROYED key with no KeyData, causing inconsistent downstream validation where functions like jwt.JWKSetFromPublicKeysetHandle() process the invalid handle and produce a JWK set, potentially misleading applications that rely on successful handle construction as proof of keyset integrity.
From the CVE record · VulnCheck