Skip to content
Fencer Intel
medium 6.5

CVE-2022-23567 json

Integer overflows in Tensorflow

published 4y ago modified last mo. also BIT-tensorflow-2022-23567 , EUVD-2022-0315 , GHSA-rrx2-r989-2c43 , PYSEC-2022-131 , PYSEC-2022-76 , PYSEC-2026-3240

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

Tensorflow is an Open Source Machine Learning Framework. The implementations of `Sparse*Cwise*` ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or `CHECK`-fails when building new `TensorShape` objects (so, assert failures based denial of service). We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. 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.

Patch / fix

  • pypi tensorflow 2.5.3, 2.6.3, 2.7.1
  • pypi tensorflow-cpu 2.5.3, 2.6.3, 2.7.1
  • pypi tensorflow-gpu 2.5.3, 2.6.3, 2.7.1
  • bitnami tensorflow 2.5.3, 2.6.3, 2.7.1

Is CVE-2022-23567 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.5.3
>=2.6.0, <2.6.3
>=2.7.0, <2.7.1
2.5.3
2.6.3
2.7.1
pypi tensorflow-cpu
<2.5.3
>=2.6.0, <2.6.3
>=2.7.0, <2.7.1
2.5.3
2.6.3
2.7.1
pypi tensorflow-gpu
<2.5.3
>=2.6.0, <2.6.3
>=2.7.0, <2.7.1
2.5.3
2.6.3
2.7.1
bitnami tensorflow
<2.5.3
>=2.6.0, <2.6.3
>=2.7.0, <2.7.1
2.5.3
2.6.3
2.7.1

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.