Vulnerability in tensorflow (CVE-2022-29195)
Summary
Vulnerability in tensorflow (CVE-2022-29195). Risk of unauthorized operations or information disclosure. Exploitable via tf.raw_ops.StagePeek. Mitigation: upgrade to 2.8.1 or later.
Original description
The description as published by the source.
Impact
The implementation of tf.raw_ops.StagePeek does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack:
import tensorflow as tf
index = tf.constant([], shape=[0], dtype=tf.int32)
tf.raw_ops.StagePeek(index=index, dtypes=[tf.int32])
The code assumes index is a scalar but there is no validation for this before accessing its value:
std::size_t index = ctx->input(0).scalar()();
Patches
We have patched the issue in GitHub commit cebe3c45d76357d201c65bdbbf0dbe6e8a63bbdb.
The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.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 Neophytos Christou from Secure Systems Lab at Brown University.
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-2022-29195 has been found in tensorflow.
Attackers can target a specific entry point like tf.raw_ops.StagePeek over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tensorflow to 2.8.1 or later.
If unsure, ask your IT team or search "tensorflow CVE-2022-29195" on the vendor's site.
CVE-2022-29195 (tensorflow) — CWE-20
Attack vector: local / no user interaction
Attack surface: tf.raw_ops.StagePeek / CHECK / index
Patched: 2.8.1 — 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-20) exists in tensorflow. Attackers reach the vulnerable code path via tf.raw_ops.StagePeek.
Check the vendor advisory for the affected versions of tensorflow. Attack surface: tf.raw_ops.StagePeek / CHECK / index.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.8.1.
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.8.1ステージング環境で 2.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com