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.
Remediation
References
https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899
https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r
Related Vulnerabilities
CVE-2020-36377 Vulnerability in npm package aaptjs
CVE-2022-34113 Vulnerability in maven package io.dataease:dataease-plugin-common
CVE-2023-30520 Vulnerability in maven package org.jenkins-ci.plugins:quayio-trigger
CVE-2014-0072 Vulnerability in npm package cordova-plugin-file-transfer
CVE-2020-26939 Vulnerability in maven package org.bouncycastle:bcprov-ext-jdk15on