Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tink-crypto | tink-go | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tink-crypto | Tink-go |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.193% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google tink Go |
|
| CPEs | cpe:2.3:a:google:tink_go:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Google
Google tink Go |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tink-crypto
Tink-crypto tink-go |
|
| Vendors & Products |
Tink-crypto
Tink-crypto tink-go |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets | |
| Weaknesses | CWE-1286 | |
| References |
| |
| Metrics |
cvssV3_1
|