CVE-2022-23583
Description
Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that any binary op would trigger `CHECK` failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the `dtype` no longer matches the `dtype` expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If `Tin` and `Tout` don't match the type of data in `out` and `input_*` tensors then `flat<*>` would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a `CHECK` crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | <2.5.3 | 2.5.3 |
| PyPI | tensorflow | >=2.6.0,<2.6.3 | 2.6.3 |
| PyPI | tensorflow | >=2.7.0,<2.7.1 | 2.7.1 |
| PyPI | tensorflow-cpu | <2.5.3 | 2.5.3 |
| PyPI | tensorflow-cpu | >=2.6.0,<2.6.3 | 2.6.3 |
| PyPI | tensorflow-cpu | >=2.7.0,<2.7.1 | 2.7.1 |
| PyPI | tensorflow-gpu | <2.5.3 | 2.5.3 |
| PyPI | tensorflow-gpu | >=2.6.0,<2.6.3 | 2.6.3 |
| PyPI | tensorflow-gpu | >=2.7.0,<2.7.1 | 2.7.1 |
| PyPI | tensorflow-gpu | <a7c02f1a9bbc35473969618a09ee5f9f5d3e52d9||>=2.6.0,<2.6.3 | a7c02f1a9bbc35473969618a09ee5f9f5d3e52d9 |
| PyPI | tensorflow-cpu | <a7c02f1a9bbc35473969618a09ee5f9f5d3e52d9||>=2.6.0,<2.6.3 | a7c02f1a9bbc35473969618a09ee5f9f5d3e52d9 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gjqc-q9g6-q2j3
- https://nvd.nist.gov/vuln/detail/CVE-2022-23583
- https://github.com/tensorflow/tensorflow/commit/a7c02f1a9bbc35473969618a09ee5f9f5d3e52d9
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-92.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-147.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/kernels/cwise_ops_common.h#L88-L137
- https://security-tracker.debian.org/tracker/CVE-2022-23583
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.