Approved changes feed: RSS · Atom
cpe:2.3:a:google:tink_java:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Google (f181d1eb-7269-5bae-b76e-e66ceb214562) |
|---|---|
| Product | Tink Java (b1b5626c-0aa7-5a91-9e3b-4f11dd970cec) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/tink-crypto/tink-java |
purl2cpe | 2026-06-01 10:16:38.807614 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-8929 |
vulnerable | 2026-06-08 05:27:19.988507 |
Ciphertext integrity weakness in Tink
MEDIUM (5.3)
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: 2020-10-19T12:15:16.000Z
Updated: 2024-08-04T10:12:11.052Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.