CVE-2022-23578

Vulnerability in tensorflow (CVE-2022-23578)

Summary

Vulnerability in tensorflow (CVE-2022-23578). Risk of unauthorized operations or information disclosure. Exploitable via nullptr. Mitigation: upgrade to 2.7.1 or later.

Original description

The description as published by the source.

Impact

If a graph node is invalid, TensorFlow can leak memory in the implementation of ImmutableExecutorState::Initialize:

Status s = params_.create_kernel(n->properties(), &item->kernel);
if (!s.ok()) {
  item->kernel = nullptr;
  s = AttachDef(s, *n);
  return s;           
}

Here, we set item->kernel to nullptr but it is a simple OpKernel* pointer so the memory that was previously allocated to it would leak.

Patches

We have patched the issue in GitHub commit c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd.
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 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-23578 has been found in tensorflow.
Attackers can target a specific entry point like nullptr over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tensorflow to 2.7.1 or later.
If unsure, ask your IT team or search "tensorflow CVE-2022-23578" on the vendor's site.

CVE-2022-23578 (tensorflow) — CWE-401
Attack vector: remote (network-reachable) / no user interaction
Attack surface: nullptr
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.

❓ What is the problem

A vulnerability (CWE-401) exists in tensorflow. Attackers reach the vulnerable code path via nullptr.

📍 Affected scope

Check the vendor advisory for the affected versions of tensorflow. Attack surface: nullptr.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.7.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

1
Identify exposure identify
```
grep -r 'tensorflow' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で tensorflow を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade tensorflow to 2.7.1
```
ステージング環境で 2.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI tensorflow

[{"type":"ECOSYSTEM","events":[{"introduced":"2.7.0"},{"fixed":"2.7.1"}]}]

PyPI tensorflow-cpu

[{"type":"ECOSYSTEM","events":[{"introduced":"2.7.0"},{"fixed":"2.7.1"}]}]

PyPI tensorflow-gpu

[{"type":"ECOSYSTEM","events":[{"introduced":"2.7.0"},{"fixed":"2.7.1"}]}]

References

Metadata

CVE: CVE-2022-23578
GHSA: GHSA-8r7c-3cm2-3h8f
Published: 2022-02-10
First seen on SecPulse: 4 years ago
First-seen source: OSV.dev (Open Source Vulnerabilities)

CWE

CWE-401

Detection sources

OSV.dev (Open Source Vulnerabilities) 3 months ago