Lucene search

K
githubGitHub Advisory DatabaseGHSA-HHVC-G5HV-48C6
HistoryDec 10, 2020 - 7:07 p.m.

Write to immutable memory region in TensorFlow

2020-12-1019:07:28
CWE-471
GitHub Advisory Database
github.com
103
tensorflow
memory region
immutable
crash
python interpreter
segmentation fault
github commit
patch
security guide
aivul team
qihoo 360
tensorflow 2.4.0
tensorflow versions
nightly packages
vulnerability
security model

CVSS2

3.6

Attack Vector

LOCAL

Attack Complexity

LOW

Authentication

NONE

Confidentiality Impact

NONE

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:L/AC:L/Au:N/C:N/I:P/A:P

CVSS3

4.4

Attack Vector

LOCAL

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

LOW

Availability Impact

LOW

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

EPSS

0

Percentile

12.8%

Impact

The tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area:

>>> import tensorflow as tf
>>> with open('/tmp/test.txt','w') as f: f.write('a'*128)
>>> tf.raw_ops.ImmutableConst(dtype=tf.string,shape=2,
                              memory_region_name='/tmp/test.txt')

If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault.

This is because the alocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overriden.

Patches

We have patched the issue in GitHub commit c1e1fc899ad5f8c725dcbb6470069890b5060bc7 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.

Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

Affected configurations

Vulners
Node
tensorflow-gpuRange2.3.02.3.2
OR
tensorflow-gpuRange2.2.02.2.2
OR
tensorflow-gpuRange2.1.02.1.3
OR
tensorflow-gpuRange2.0.02.0.4
OR
tensorflow-gpuRange<1.15.5
OR
tensorflow-cpuRange2.3.02.3.2
OR
tensorflow-cpuRange2.2.02.2.2
OR
tensorflow-cpuRange2.1.02.1.3
OR
tensorflow-cpuRange2.0.02.0.4
OR
tensorflow-cpuRange<1.15.5
OR
tensorflowtensorflowRange2.3.02.3.2
OR
tensorflowtensorflowRange2.2.02.2.2
OR
tensorflowtensorflowRange2.1.02.1.3
OR
tensorflowtensorflowRange2.0.02.0.4
OR
tensorflowtensorflowRange<1.15.5
VendorProductVersionCPE
*tensorflow-gpu*cpe:2.3:a:*:tensorflow-gpu:*:*:*:*:*:*:*:*
*tensorflow-cpu*cpe:2.3:a:*:tensorflow-cpu:*:*:*:*:*:*:*:*
tensorflowtensorflow*cpe:2.3:a:tensorflow:tensorflow:*:*:*:*:*:*:*:*

CVSS2

3.6

Attack Vector

LOCAL

Attack Complexity

LOW

Authentication

NONE

Confidentiality Impact

NONE

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:L/AC:L/Au:N/C:N/I:P/A:P

CVSS3

4.4

Attack Vector

LOCAL

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

LOW

Availability Impact

LOW

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

EPSS

0

Percentile

12.8%