medium5.3
CVE-2020-8929
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,…
Impact
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 products
| Vendor | Product | Affected versions |
|---|---|---|
| Tink Java | before 1.5.0 |
Weakness classification
References
- NVD record
- CVE.org record
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r