Vulnerability in com.google.crypto.tink:tink (CVE-2020-8929)
Summary
Vulnerability in com.google.crypto.tink:tink (CVE-2020-8929). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.0 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-8929 has been found in com.google.crypto.tink:tink.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.google.crypto.tink:tink to 1.5.0 or later.
If unsure, ask your IT team or search "com.google.crypto.tink:tink CVE-2020-8929" on the vendor's site.
CVE-2020-8929 (com.google.crypto.tink:tink) — CWE-176
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-176) exists in com.google.crypto.tink:tink.
Check the vendor advisory for the affected versions of com.google.crypto.tink:tink.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.google.crypto.tink:tink を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.google.crypto.tink:tink to 1.5.0ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com