Vulnerabilities · 2020 · Google
CVE-2020-8929
Google Tink Java vulnerability
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
Tink Java. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Tink Java runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 · Patch
- github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r · Patch
- nvd.nist.gov/vuln/detail/CVE-2020-8929
- github.com/pypa/advisory-database/tree/main/vulns/tink/PYSEC-2020-142.yaml
- github.com/advisories/GHSA-g5vf-v6wf-7w2r
- nvd.nist.gov/vuln/detail/CVE-2020-8929
- cve.org/CVERecord?id=CVE-2020-8929
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.