CVE-2020-8929 - CVE House
Back to Database
Status published Medium CVE-2020-8929

Ciphertext integrity weakness in Tink

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

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-8929

Credits & Attribution

The following person or organization is credited with identifying this vulnerability, as recorded in the NVD database:

  • Peter Esbensen

References

More from Google LLC

View All →
CVE-2022-3474
Bazel leaks user credentials through the remote assets API
Medium 5.1
CVE-2022-3421
Privilege escalation in Google Drive for Desktop on MacOS
Medium 5.6
CVE-2022-3171
Memory handling vulnerability in ProtocolBuffers Java core and lite
Medium 4.3
CVE-2022-3095
Incorrect parsing of the backslash characters in Dart library
Critical 9.8
CVE-2022-2390
Mutable pending intent in Google Play services SDK
Medium 6.1

Affected Vendor

Affected Software

Tink
Vulnerable Versions:
stable

Timeline

Official Publish: October 19th, 2020
Last Modified: August 4th, 2024
Added to House: July 21st, 2026

CVSS Vectors

V3: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Weaknesses (CWE)

CWE-176

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.