Vulnerability in Google Tink Java
CVE-2020-8929
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.
EPSS: 0.005 (37.7th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
Affected products
- Google Tink_java
- Google Llc Tink — versions stable
Weakness classification (CWE)
References
- cve-coordination@google.com (x_refsource_CONFIRM, Patch, Third Party Advisory)
- cve-coordination@google.com (x_refsource_CONFIRM, Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-8929?
- CVE-2020-8929 is a medium-severity vulnerability in Google Tink Java, classified under CWE-176. CVSS score: 5.3/10. Published 2020-10-19.
- How severe is CVE-2020-8929?
- Medium severity. CVSS v3 base score is 5.3 out of 10.