CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Google

CVE-2020-8929
Google Tink Java vulnerability

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.

Affected products

Tink Java. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Google Tink Java runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Google products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.