CVE-2021-37691

Process crash via zero-sized LSH input

Published Aug 12, 2021 · Updated Aug 4, 2024

Divide-by-zero in TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to crash TFLite via a crafted model. The LSH projection kernel's RunningSignBit routine divides input bytes by a first-dimension size that can be zero because Resize checks only that a dimension exists, not that its size is positive. Processing an attacker-supplied TFLite model is required, and the demonstrated consequence is termination of the consuming process without data disclosure or modification.

CVSS severity5.5
Medium
EPSS probability0.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Divide-by-zero in TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to crash TFLite via a crafted model. The LSH projection kernel's RunningSignBit routine divides input bytes by a first-dimension size that can be zero because Resize checks only that a dimension exists, not that its size is positive. Processing an attacker-supplied TFLite model is required, and the demonstrated consequence is termination of the consuming process without data disclosure or modification.

The record

CVE
CVE-2021-37691
Published
Aug 12, 2021
Updated
Aug 4, 2024
Vendor
Google
Product
TensorFlow
Classifications
CWE-369, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 12, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.3.4
  2. Affected versionversion=>= 2.4.0, < 2.4.3
  3. Affected versionversion=>= 2.5.0, < 2.5.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Google · TensorFlowversion=< 2.3.4; version=>= 2.4.0, < 2.4.3; version=>= 2.5.0, < 2.5.1

Published CVSS scores

2.1NIST NVDAV:L/AC:L/Au:N/C:N/I:N/A:P
5.5GitHub, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-369Divide By Zero
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo