Vulnerability in tensorflow (CVE-2020-15191)
Summary
Vulnerability in tensorflow (CVE-2020-15191). Risk of unauthorized operations or information disclosure. Exploitable via dlpack.to_dlpack. Mitigation: upgrade to 2.3.1 or later.
Original description
The description as published by the source.
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to dlpack.to_dlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with -fsanitize=null. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.
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-2020-15191 has been found in tensorflow.
Attackers can target a specific entry point like dlpack.to_dlpack over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tensorflow to 2.3.1 or later.
If unsure, ask your IT team or search "tensorflow CVE-2020-15191" on the vendor's site.
CVE-2020-15191 (tensorflow) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: dlpack.to_dlpack / nullptr / status
Patched: 2.3.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 dlpack.to_dlpack without authentication.
Check the vendor advisory for the affected versions of tensorflow. Attack surface: dlpack.to_dlpack / nullptr / status.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.3.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.3.1ステージング環境で 2.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory lists.opensuse.org
- package github.com
- patch github.com
- report github.com
- web github.com
- web github.com
- web github.com