CVE-2020-8929

Ciphertext integrity weakness in Tink

State
Published
Severity
5.3 Medium
Published
Oct 19, 2020
Updated
Aug 4, 2024
Reserved
Feb 12, 2020

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.15.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NGoogle

Weaknesses

  • CWE-176 Improper Handling of Unicode Encoding

Affected Products

ProductVersions
TinkGoogle LLC
  • stable to before 1.5Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.