CVE-2020-8929
Medium
Description
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.
SeverityMedium
CVSS5.3
Exploit probability—
Product
Google Tink Java
PublishedOct 19, 2020
First seenOct 19, 2020
Weakness typeCWE-176CWE-176
How to fix
Update
- google tink_java1.5.0 or later
- tink1.5.0 or later
- com.google.crypto.tink:tink1.5.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| google tink_java | v < 1.5.0 | 1.5.0 |
| tinkPyPI | v < 1.5.0 | 1.5.0 |
| com.google.crypto.tink:tinkMaven | v < 1.5.0 | 1.5.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.