Out-of-Bounds Read in tensorflow (CVE-2022-23592)
Summary
Vulnerability in tensorflow (CVE-2022-23592). Confidential information can be exposed externally. Exploitable via DCHECK. Mitigation: upgrade to 2.8.0 or later.
Original description
The description as published by the source.
Tensorflow is an Open Source Machine Learning Framework. TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a DCHECK (which is a no-op during production). An attacker can control the input_idx variable such that ix would be larger than the number of values in node_t.args. The fix will be included in TensorFlow 2.8.0. This is the only affected version.
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-23592 has been found in tensorflow.
Attackers can target a specific entry point like DCHECK over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade tensorflow to 2.8.0 or later.
If unsure, ask your IT team or search "tensorflow CVE-2022-23592" on the vendor's site.
CVE-2022-23592 (tensorflow) — CWE-125
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DCHECK / input_idx / node_t.args
Patched: 2.8.0 — 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.
Out-of-bounds read (CWE-125) exists in tensorflow. Attackers reach the vulnerable code path via DCHECK.
Check the vendor advisory for the affected versions of tensorflow. Attack surface: DCHECK / input_idx / node_t.args.
Severity: ?. Confidential information can be exposed externally.
Update to 2.8.0.
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.0ステージング環境で 2.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com