Out-of-Bounds Read in tensorflow (CVE-2022-23574)
Summary
Vulnerability in tensorflow (CVE-2022-23574). Successful exploitation can lead to full system takeover. Exploitable via SpecializeType. Mitigation: upgrade to 2.7.1 or later.
Original description
The description as published by the source.
Impact
There is a typo in TensorFlow's SpecializeType which results in heap OOB read/write:
for (int i = 0; i < op_def.output_arg_size(); i++) {
// ...
for (int j = 0; j < t->args_size(); j++) {
auto* arg = t->mutable_args(i);
// ...
}
}
Due to a typo, arg is initialized to the ith mutable argument in a loop where the loop index is j. Hence it is possible to assign to arg from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data.
Patches
We have patched the issue in GitHub commit 0657c83d08845cc434175934c642299de2c0f042.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, 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.
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-23574 has been found in tensorflow.
Attackers can target a specific entry point like SpecializeType over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade tensorflow to 2.7.1 or later.
If unsure, ask your IT team or search "tensorflow CVE-2022-23574" on the vendor's site.
CVE-2022-23574 (tensorflow) — CWE-125
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SpecializeType / arg
Patched: 2.7.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.
Out-of-bounds read (CWE-125) exists in tensorflow. Attackers reach the vulnerable code path via SpecializeType.
Check the vendor advisory for the affected versions of tensorflow. Attack surface: SpecializeType / arg.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.7.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.7.1ステージング環境で 2.7.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