tensorflow
Affected
- introduced
0, fixed2.3.4(ecosystem)
Fixed versions
2.3.4
Fix
- Fixed version
2.3.4pip install --upgrade tensorflow==2.3.4
Advisory
Also known as: BIT-tensorflow-2021-37652, CVE-2021-37652, PYSEC-2021-274, PYSEC-2021-565, PYSEC-2021-763
Use after free in boosted trees creation
Impact
The implementation for tf.raw_ops.BoostedTreesCreateEnsemble can result in a use after free error if an attacker supplies specially crafted arguments:
import tensorflow as tf
v= tf.Variable([0.0])
tf.raw_ops.BoostedTreesCreateEnsemble(
tree_ensemble_handle=v.handle,
stamp_token=[0],
tree_ensemble_serialized=['0'])
The implementation uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent free-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed.
Patches
We have patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab.
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
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.
High Basis: The source's own band: HIGH
0, fixed 2.3.4 (ecosystem)2.3.4
2.3.4pip install --upgrade tensorflow==2.3.42.4.0, fixed 2.4.3 (ecosystem)2.4.3
2.4.3pip install --upgrade tensorflow==2.4.32.5.0, fixed 2.5.1 (ecosystem)2.5.1
2.5.1pip install --upgrade tensorflow==2.5.10, fixed 2.3.4 (ecosystem)2.3.4
2.3.4pip install --upgrade tensorflow-cpu==2.3.42.4.0, fixed 2.4.3 (ecosystem)2.4.3
2.4.3pip install --upgrade tensorflow-cpu==2.4.32.5.0, fixed 2.5.1 (ecosystem)2.5.1
2.5.1pip install --upgrade tensorflow-cpu==2.5.10, fixed 2.3.4 (ecosystem)2.3.4
2.3.4pip install --upgrade tensorflow-gpu==2.3.42.4.0, fixed 2.4.3 (ecosystem)2.4.3
2.4.3pip install --upgrade tensorflow-gpu==2.4.32.5.0, fixed 2.5.1 (ecosystem)2.5.1
2.5.1pip install --upgrade tensorflow-gpu==2.5.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0