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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tink Java | < 1.5.0 |
Related Weaknesses (CWE)
References
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899PatchThird Party Advisory
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2rPatchThird Party Advisory
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899PatchThird Party Advisory
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2rPatchThird Party Advisory
FAQ
What is CVE-2020-8929?
CVE-2020-8929 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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...
How severe is CVE-2020-8929?
CVE-2020-8929 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-8929?
Check the references section above for vendor advisories and patch information. Affected products include: Google Tink Java.