CVE-2020-8929 vulnerability in Google Products
Published on October 19, 2020
Ciphertext integrity weakness in Tink
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.
Vulnerability Analysis
CVE-2020-8929 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality, with no impact on integrity, and no impact on availability.
Weakness Type
Improper Handling of Unicode Encoding
The software does not properly handle when an input contains Unicode encoding.
Products Associated with CVE-2020-8929
stack.watch emails you whenever new vulnerabilities are published in Google Tink or Google Tink Java. Just hit a watch button to start following.
Affected Versions
Google LLC Tink:- Version stable and below 1.5 is affected.
Vulnerable Packages
The following package name and versions may be associated with CVE-2020-8929
| Package Manager | Vulnerable Package | Versions | Fixed In |
|---|---|---|---|
| maven | com.google.crypto.tink:tink | < 1.5.0 | 1.5.0 |
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.