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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-0220 | Ciphertext Malleability Issue in Tink Java |
Github GHSA |
GHSA-g5vf-v6wf-7w2r | Ciphertext Malleability Issue in Tink Java |
References
History
Thu, 05 Jun 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google tink Java
|
|
| CPEs | cpe:2.3:a:google:tink_java:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Google tink
|
Google tink Java
|
Status: PUBLISHED
Assigner: Google
Published:
Updated: 2024-08-04T10:12:11.052Z
Reserved: 2020-02-12T00:00:00.000Z
Link: CVE-2020-8929
No data.
Status : Analyzed
Published: 2020-10-19T13:15:13.437
Modified: 2025-06-05T14:50:15.710
Link: CVE-2020-8929
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA