PYSEC-2020-142

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...

CVE-2020-8929

CVE-2020-8929 concerns the Java implementation of Google Tink prior to 1.5, where mis-handling invalid Unicode characters in ciphertexts allows an attacker to change the ID portion of a ciphertext. This can create a second ciphertext that decrypts to the same plaintext, impacting ciphertext integ...

CVE-2020-8929 Ciphertext integrity weakness in Tink

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...

Malleable Ciphertext

tink has a ciphertext malleability issue. The vulnerability exists due to storing of the ciphertext prefix in a hashmap keyed by a UTF8 encoded string instead of using byte arrays, allowing the retrieval of keys with IDs of invalid Unicode strings with a changed ID...

Ciphertext Malleability Issue in Tink Java

Impact Tink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a...

GHSA-G5VF-V6WF-7W2R Ciphertext Malleability Issue in Tink Java

Impact Tink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a...

PT-2020-20372 · Google · Tink

Name of the Vulnerable Software and Affected Versions: Tink versions prior to 1.5 Description: A mis-handling of invalid unicode characters in the Java implementation of Tink allows an attacker to change the ID part of a ciphertext, resulting in the creation of a second ciphertext that can decryp...

NaCl Is Not a High-Level API

When talking about high-level application cryptography APIs I usually hear mentioned libsodium, Tink, pyca/cryptography, and NaCl. One of these things is not like the others! The value NaCl had 10 years ago was that it was an opinionated library at a time when all cryptography libraries were...