Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2020-15202 | First vendor Publication | 2020-09-25 |
| Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 9 | ||
| Base Score | 9 | Environmental Score | 9 |
| impact SubScore | 6 | Temporal Score | 9 |
| Exploitabality Sub Score | 2.2 | ||
| Attack Vector | Network | Attack Complexity | High |
| Privileges Required | None | User Interaction | None |
| Scope | Changed | Confidentiality Impact | High |
| Integrity Impact | High | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : (AV:N/AC:M/Au:N/C:P/I:P/A:P) | |||
|---|---|---|---|
| Cvss Base Score | 6.8 | Attack Range | Network |
| Cvss Impact Score | 6.4 | Attack Complexity | Medium |
| Cvss Expoit Score | 8.6 | Authentication | None Required |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15202 |
CPE : Common Platform Enumeration
| Type | Description | Count |
|---|---|---|
| Application | 5 | |
| Os | 1 |
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2024-11-28 13:40:11 |
|
| 2021-11-18 21:24:22 |
|
| 2021-09-16 21:23:44 |
|
| 2021-08-19 09:23:01 |
|
| 2021-08-18 01:43:26 |
|
| 2021-08-18 01:37:23 |
|
| 2021-08-17 21:23:24 |
|
| 2021-08-17 17:22:59 |
|
| 2021-05-05 01:38:17 |
|
| 2021-05-04 13:46:53 |
|
| 2021-04-22 02:58:44 |
|
| 2020-12-15 01:28:44 |
|
| 2020-11-01 17:22:56 |
|
| 2020-10-02 00:22:50 |
|
| 2020-10-01 21:23:06 |
|
| 2020-09-26 09:22:47 |
|
| 2020-09-26 00:22:48 |
|
