CVE-2020-8929
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.
Risk Information
Base Score
5.3
MODERATE
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score
Exploitation Probability
0.081
Associated Vulnerability
| Vulnerability | OS Platform |
|---|---|
| Vulnerabilities CVE-2020-8929 are fixed in Google - tink 1.5.0 | Windows |
| Vulnerabilities CVE-2020-8929 are fixed in Python-tink 1.5.0 | Windows |
| Vulnerabilities CVE-2020-8929 are fixed in Google - tink for Linux 1.5.0 | Linux |
| Vulnerabilities CVE-2020-8929 are fixed in Python-tink for linux 1.5.0 | Linux |
Patch Details
No records foundReferences
https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234