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.
References
Link | Resource |
---|---|
https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 | Patch Third Party Advisory |
https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r | Patch Third Party Advisory |
https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 | Patch Third Party Advisory |
https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r | Patch Third Party Advisory |
Configurations
History
21 Nov 2024, 05:39
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 - Patch, Third Party Advisory | |
References | () https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r - Patch, Third Party Advisory |
Information
Published : 2020-10-19 13:15
Updated : 2024-11-21 05:39
NVD link : CVE-2020-8929
Mitre link : CVE-2020-8929
CVE.ORG link : CVE-2020-8929
JSON object : View
Products Affected
- tink
CWE