Skip to content

CVE-2020-8929 Ciphertext integrity weakness in Tink

MediumCVSS 5.3 EPSS 0.46%
Published
Updated
Exploit status
No public exploit known

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.

Affected products

ProductAffected versionsFixed in
pypi tink(PyPI) < 1.5.0 1.5.0
pypi tink(PyPI) = 1.4.0 No fix listed
com.google.crypto.tink/tink(Maven) < 1.5.0 1.5.0
com.google.crypto.tink/tink(Maven) = 1.0.0 No fix listed
com.google.crypto.tink/tink(Maven) = 1.1.0 No fix listed
com.google.crypto.tink/tink(Maven) = 1.1.1 No fix listed
com.google.crypto.tink/tink(Maven) = 1.2.0 No fix listed
com.google.crypto.tink/tink(Maven) = 1.2.0-rc2 No fix listed
com.google.crypto.tink/tink(Maven) = 1.2.0-rc3 No fix listed
com.google.crypto.tink/tink(Maven) = 1.2.0-rc4 No fix listed
com.google.crypto.tink/tink(Maven) = 1.2.1 No fix listed
com.google.crypto.tink/tink(Maven) = 1.2.2 No fix listed
com.google.crypto.tink/tink(Maven) = 1.3.0 No fix listed
com.google.crypto.tink/tink(Maven) = 1.3.0-rc1 No fix listed
com.google.crypto.tink/tink(Maven) = 1.3.0-rc2 No fix listed
com.google.crypto.tink/tink(Maven) = 1.3.0-rc3 No fix listed
com.google.crypto.tink/tink(Maven) = 1.3.0-rc4 No fix listed
com.google.crypto.tink/tink(Maven) = 1.4.0 No fix listed
com.google.crypto.tink/tink(Maven) = 1.4.0-rc1 No fix listed
com.google.crypto.tink/tink(Maven) = 1.4.0-rc2 No fix listed
Google tink java < 1.5.0 1.5.0
Google Tink >= stable, < 1.5 1.5

References