WaratekVRT Sign in

CVE-2020-8929

Severity5.3 Medium CVSS 3.1 3 scores
Fixed in1.5.0
WeaknessCWE-176
Published19 Oct 2020
Updated17 Jun 2026

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.

CWE-327

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 6 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS 0.46% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: google/tink 93d839a.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.
Candidate fix https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 : a commit: the change itself

CVSS

5.3 MEDIUM v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N 3 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 5.3 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N cve-coordination@google.com Secondary published
CVSS 3.1 5.3 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N NVD Primary
CVSS 2.0 5.0 none AV:N/AC:L/Au:N/C:N/I:P/A:N NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
com.google.crypto.tink:tink 0 1.5.0 unbounded

Products and versions

2 products, 2 version entries
SourceVendorProductSchemeAffected versions
osv com.google.crypto.tink tink generic < 1.5.0
nvd google tink java generic < 1.5.0

References

URLTags
https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899 commit
https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r WEB
https://github.com/pypa/advisory-database/tree/main/vulns/tink/PYSEC-2020-142.yaml WEB

Timeline

Published2020-10-19By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.