published 19 Oct 2020 · updated 4 Aug 2024
Ciphertext integrity weakness in Tink
5.3MediumCVSS 5.3EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Tink 1.5.
A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Tink | >=stable <1.5 | 1.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Google, strongest first
Embed
A live severity badge for an advisory, README or ticket