Observable Timing Discrepancy in Tink-Java and Tink-Android ChunkedMacVerification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Tink-Java | unaffected |
|
|||||||
| Tink-Android | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tink Android |
|
|||||||||
| Tink Java |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.183% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/tink-crypto/tink-java/issues/75 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:google:tink_java:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google tink Android Google tink Java |
|
| Vendors & Products |
Google
Google tink Android Google tink Java |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Observable Timing Discrepancy in Tink-Java and Tink-Android ChunkedMacVerification | |
| Weaknesses | CWE-208 | |
| References |
| |
| Metrics |
cvssV4_0
|