Approved changes feed: RSS · Atom
cpe:2.3:a:google:tink:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Google (f181d1eb-7269-5bae-b76e-e66ceb214562) |
|---|---|
| Product | Tink (2cfb4995-3ea0-5078-b5a8-77fa1e7cb152) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/google/tink |
purl2cpe | 2026-06-01 10:16:38.517171 |
pkg:googlesource/tink |
purl2cpe | 2026-06-01 10:16:38.517173 |
pkg:maven/com.google.crypto.tink/tink |
purl2cpe | 2026-06-01 10:16:38.517175 |
pkg:pypi/tink |
purl2cpe | 2026-06-01 10:16:38.517177 |
pkg:sourceforge/tink.mirror |
purl2cpe | 2026-06-01 10:16:38.517179 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-4420 |
vulnerable | 2026-06-08 06:50:17.728520 |
Denial of Service in Tink-cc
There exists a Denial of service vulnerability in Tink-cc in versions prior to 2.1.3. * An adversary can crash binaries using the crypto::tink::JsonKeysetReader in tink-cc by providing an input that is not an encoded JSON object, but still a valid encoded JSON element, for example a number or an array. This will crash as Tink just assumes any valid JSON input will contain an object.
* An adversary can crash binaries using the crypto::tink::JsonKeysetReader in tink-cc by providing an input containing many nested JSON objects. This may result in a stack overflow.
We recommend upgrading to version 2.1.3 or above
Published: 2024-05-21T11:52:28.398Z
Updated: 2024-08-01T20:40:47.073Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-8929 |
vulnerable | 2026-06-08 05:27:19.987725 |
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.