Vulnerability in tensorflow (CVE-2021-29554)
Summary
Vulnerability in tensorflow (CVE-2021-29554). Risk of unauthorized operations or information disclosure. Exploitable via tf.raw_ops.DenseCountSparseOutput. Mitigation: upgrade to 2.4.2 or later.
Original description
The description as published by the source.
TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in tf.raw_ops.DenseCountSparseOutput. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division. Since data is given by the values argument, num_batch_elements is 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, and TensorFlow 2.3.3, as these are also affected.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29554 has been found in tensorflow.
Attackers can target a specific entry point like tf.raw_ops.DenseCountSparseOutput over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tensorflow to 2.4.2 or later.
If unsure, ask your IT team or search "tensorflow CVE-2021-29554" on the vendor's site.
CVE-2021-29554 (tensorflow) — CWE-369
Attack vector: local / no user interaction
Attack surface: tf.raw_ops.DenseCountSparseOutput / data / values / num_batch_elements
Patched: 2.4.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-369) exists in tensorflow. Attackers reach the vulnerable code path via tf.raw_ops.DenseCountSparseOutput.
Check the vendor advisory for the affected versions of tensorflow. Attack surface: tf.raw_ops.DenseCountSparseOutput / data / values / num_batch_elements.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tensorflow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tensorflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tensorflowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tensorflow to 2.4.2ステージング環境で 2.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- package github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com