Vulnerability in GitHub commit be7a4de6adfbd303ce08be4332554… (CVE-2021-37666)

Summary

Vulnerability in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612 (CVE-2021-37666). Successful exploitation can lead to full system takeover. Exploitable via tf.raw_ops.RaggedTensorToVariant.

Original description

The description as published by the source.

TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in tf.raw_ops.RaggedTensorToVariant. The implementation has an incomplete validation of the splits values, missing the case when the argument would be empty. We have patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

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-2021-37666 has been found in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612.
Attackers can target a specific entry point like tf.raw_ops.RaggedTensorToVariant over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GitHub commit be7a4de6adfbd303ce08be4332554dff70362612 CVE-2021-37666" on the vendor's site.

CVE-2021-37666 (GitHub commit be7a4de6adfbd303ce08be4332554dff70362612)
Attack vector: local / no user interaction
Attack surface: tf.raw_ops.RaggedTensorToVariant
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 (unclassified) exists in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612. Attackers reach the vulnerable code path via tf.raw_ops.RaggedTensorToVariant.

📍 Affected scope

Check the vendor advisory for the affected versions of GitHub commit be7a4de6adfbd303ce08be4332554dff70362612. Attack surface: tf.raw_ops.RaggedTensorToVariant.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで GitHub commit be7a4de6adfbd303ce08be4332554dff70362612 を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

advisory github.com
patch github.com