Overview 6 matches · 1 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
6matches
1in Waratek scope16.7%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
1public PoC16.7%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
16.7%
Outside Waratek scope
0
0.0%
Not applicable
5
83.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
6
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
16.7%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
5
83.3%
split by
peak 2 / year
20031
Not applicable1
High1
not blocked1
Working exploit published1
20040
20052
Not applicable2
High1
Low1
not blocked2
No public exploit2
20060
20070
20080
20090
20100
20110
20120
20130
20140
20150
20160
20170
20180
20190
20201
No exploit published1
Medium1
not blocked1
No public exploit1
20210
20220
20230
20241
Not applicable1
Medium1
not blocked1
No public exploit1
20250
20261
Not applicable1
High1
not blocked1
No public exploit1
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-15432 | High | 2026-07-21 | Not applicable | No public exploit | When verifying a mac with a ChunkedMacVerification object, Tink compares the resulting tag with non constant time comparison. This potentially allows an attacker to use timinig information as a side channel in order to get information how many bytes of a given tag match the correct tag. This in turn could allow to find a correct tag bytewise. |
| CVE-2024-4420 | Medium | 2024-05-21 | Not applicable | No public exploit | 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 |
| CVE-2020-8929 | Medium | 2020-10-19 | No exploit published | No public exploit | 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. |
| CVE-2005-4604 | High | 2005-12-31 | Not applicable | No public exploit | Buffer overflow in MTink in the printer-filters-utils package allows local users to execute arbitrary code via a long HOME environment variable. |
| CVE-2004-1110 | Low | 2005-01-10 | Not applicable | No public exploit | The mtink status monitor before 1.0.5 for Epson printers allows local users to overwrite arbitrary files via a symlink attack on the epson temporary file. |
| CVE-2003-0034 | High | 2003-02-07 | Not applicable | Working exploit published | Buffer overflow in the mtink status monitor, as included in the printer-drivers package in Mandrake Linux, allows local users to execute arbitrary code via a long HOME environment variable. |