Vulnerability in Google Tink Java
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. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS: 0.005 (37.8th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 38th percentile — 37.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.005 · newest: 0.005 · change: 0.000
Affected products
- Google Tink Java
- Google Llc Tink — versions stable
Weakness classification (CWE)
References
- github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 (Patch, Third Party Advisory)
- github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r (Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-8929?
- CVE-2020-8929 is a medium-severity vulnerability in Google Tink Java, classified under CWE-176. CVSS score: 5.3/10. Published 2020-10-19.
- How severe is CVE-2020-8929?
- Medium severity. CVSS v3 base score is 5.3 out of 10.