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-2016-2166 Vulnerability in maven package org.apache.qpid:proton-j
CVE-2023-47320 Vulnerability in maven package org.silverpeas.core:silverpeas-core-war
CVE-2019-3875 Vulnerability in maven package org.keycloak:keycloak-services
CVE-2021-43783 Vulnerability in npm package @backstage/plugin-scaffolder-backend
CVE-2022-41250 Vulnerability in maven package com.meowlomo.jenkins:scm-httpclient