Skip to content
Noroxi
OSV ecosystem advisory

GHSA-43q8-3fv7-pr5x: Improper Validation of Integrity Check Value in TensorFlow

HighCVSS 7.0 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: tensorflow (PyPI) 2.6.3, 2.7.1, 2.5.3; tensorflow-cpu (PyPI) 2.6.3, 2.7.1, 2.5.3; tensorflow-gpu (PyPI) 2.6.3, 2.7.1, 2.5.3.

Low priority for now. Upgrade to tensorflow (PyPI) 2.6.3, 2.7.1, 2.5.3; tensorflow-cpu (PyPI) 2.6.3, 2.7.1, 2.5.3; tensorflow-gpu (PyPI) 2.6.3, 2.7.1, 2.5.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### Impact The implementation of [`tf.sparse.split`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_split_op.cc#L26-L102) does not fully validate the input arguments. Hence, a malicious user can trigger a denial of service via a segfault or a heap OOB read: ```python import tensorflow as tf data = tf.random.uniform([1, 32, 32], dtype=tf.float32) axis = [1, 2] x = tf.sparse.from_dense(data) result = tf.sparse.split(x,3, axis=axis) ``` The code assumes `axis` is a scalar. This is another instance of [TFSA-2021-190](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-190.md) (CVE-2021-41206). ### Patches We have patched the issue in GitHub commit [61bf91e768173b001d56923600b40d9a95a04ad5](https://github.com/tensorflow/tensorflow/commit/61bf91e768173b001d56923600b40d9a95a04ad5) (merging [#53695](https://github.com/tensorflow/tensorflow/pull/53695)). 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. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/53660).

Published
Feb 9, 2022
Updated
Dec 5, 2024
EPSS
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-43q8-3fv7-pr5x

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
PyPItensorflow
PyPItensorflow-cpu
PyPItensorflow-gpu

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPItensorflowfrom 2.6.0 · before 2.6.32.6.3
PyPItensorflowfrom 2.7.0 · before 2.7.12.7.1
PyPItensorflowbefore 2.5.32.5.3
PyPItensorflow-cpufrom 2.6.0 · before 2.6.32.6.3
PyPItensorflow-cpufrom 2.7.0 · before 2.7.12.7.1
PyPItensorflow-cpubefore 2.5.32.5.3
PyPItensorflow-gpufrom 2.6.0 · before 2.6.32.6.3
PyPItensorflow-gpufrom 2.7.0 · before 2.7.12.7.1
PyPItensorflow-gpubefore 2.5.32.5.3

Same product

PyPI: all records

Other highest-scoring records for the same primary product.

Published before and after this one in the same product

  • Later →GHSA-mw6j-hh29-h379May 25, 2022 · `CHECK` failure in depthwise ops via overflows
    0Monitor
  • Later →GHSA-xf83-q765-xm6mNov 21, 2022 · `CHECK` fail in `TensorListScatter` and `TensorListScatterV2` in eager mode
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
PyPI:tensorflow2.5.3Package registry (OSV)
PyPI:tensorflow2.6.3Package registry (OSV)
PyPI:tensorflow2.7.1Package registry (OSV)
PyPI:tensorflow-cpu2.5.3Package registry (OSV)
PyPI:tensorflow-cpu2.6.3Package registry (OSV)
PyPI:tensorflow-cpu2.7.1Package registry (OSV)
PyPI:tensorflow-gpu2.5.3Package registry (OSV)
PyPI:tensorflow-gpu2.6.3Package registry (OSV)
PyPI:tensorflow-gpu2.7.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

All records