BIT-tensorflow-2020-15202

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/tensorflow/BIT-tensorflow-2020-15202.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-tensorflow-2020-15202
Aliases
Published
2024-03-06T11:20:37.404Z
Modified
2024-03-06T11:25:28.861Z
Summary
[none]
Details

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.

Database specific
{
    "cpes": [
        "cpe:2.3:a:google:tensorflow:*:*:*:*:-:*:*:*"
    ],
    "severity": "Critical"
}
References

Affected packages

Bitnami / tensorflow

Package

Name
tensorflow
Purl
pkg:bitnami/tensorflow

Severity

  • 9.0 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.15.4
Introduced
2.0.0
Fixed
2.0.3
Introduced
2.1.0
Fixed
2.1.2
Introduced
2.2.0
Fixed
2.2.1
Introduced
2.3.0
Fixed
2.3.1