CVE-2020-8929
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.
Does this matter?
Lower severity and a low EPSS score (0.46%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- EPSS
- 0.46% probability · 39th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-176
- Affected
- google/tink java
- Source
- cve-coordination@google.com
References
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899Patch, Third Party Advisory
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2rPatch, Third Party Advisory
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899Patch, Third Party Advisory
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2rPatch, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.