LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37642: Division by 0 in `ResourceScatterDiv` in TensorFlow

TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.ResourceScatterDiv` is vulnerable to a division by 0 error. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. We have patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76. 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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This TensorFlow flaw can crash or disrupt workloads by triggering a division-by-zero condition in a raw tensor operation. It is not a data theft issue, but it can affect availability for ML systems using vulnerable TensorFlow versions.

Executive priority

Treat as a moderate availability risk. Patch during the next standard security update cycle, sooner for shared ML infrastructure or services where users can submit TensorFlow workloads.

Technical view

CVE-2021-37642 is a CWE-369 divide-by-zero vulnerability in tf.raw_ops.ResourceScatterDiv. TensorFlow reused common binary-operation handling but did not separately handle division by zero. The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact.

Likely exposure

Systems running TensorFlow >=2.5.0 <2.5.1, >=2.4.0 <2.4.3, or <2.3.4 are affected. Exposure is most relevant where local users, jobs, notebooks, or ML pipelines can execute TensorFlow operations.

Exploitation context

The bundle does not indicate active exploitation, and KEV is false. The CVSS vector describes local exploitation requiring low privileges and no user interaction, with availability impact only.

Researcher notes

Focus validation on dependency versions and execution boundaries. The evidence supports an availability-only divide-by-zero issue in ResourceScatterDiv; no source in the bundle supports remote exploitation, confidentiality impact, or active exploitation.

Mitigation direction

  • Upgrade TensorFlow to 2.6.0 or a fixed supported branch release.
  • Use TensorFlow 2.5.1, 2.4.3, or 2.3.4 where those branches apply.
  • Check the TensorFlow advisory for any branch-specific guidance.
  • Prioritize shared ML environments where untrusted users can run TensorFlow workloads.

Validation and detection

  • Inventory TensorFlow versions in applications, notebooks, containers, and training images.
  • Compare versions against the affected ranges listed in the advisory.
  • Confirm dependency lockfiles and deployed images contain fixed TensorFlow versions.
  • Review shared ML platforms for users able to run TensorFlow jobs locally.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-369: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37642 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-37642Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow>= 2.5.0, < 2.5.1, >= 2.4.0, < 2.4.3, < 2.3.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-369 · source CWE mapping

Divide By Zero

Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.