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-2023-36820 Vulnerability in maven package io.micronaut.security:micronaut-security-oauth2
CVE-2022-25875 Vulnerability in npm package svelte
CVE-2021-28092 Vulnerability in maven package org.webjars.npm:is-svg
CVE-2022-24772 Vulnerability in npm package node-forge
CVE-2020-5228 Vulnerability in maven package org.opencastproject:opencast-oaipmh-api