CVE-2020-8929PYSEC-2020-142GHSA-G5VF-V6WF-7W2R
Ciphertext integrity weakness in Tink
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.5, 1.5.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Google LLC Tink
From stable · fixed in 1.5
- tinkPyPI
fixed in 1.5.0
- com.google.crypto.tink:tinkMaven
fixed in 1.5.0