CVE-2021-37684
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. We have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695). 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTensorFlow Lite's pooling operations contain division by zero vulnerabilities due to missing validation checks on divisor values before performing division calculations. This could cause denial of service via crafted inputs that trigger unhandled division-by-zero errors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.3.0, < 2.3.4>= 2.4.0, < 2.4.3= 2.5.0= 2.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify TensorFlow versionRun 'python -c "import tensorflow as tf; print(tf.__version__)"' to get the installed TensorFlow versionAffected if Version is 2.3.0-2.3.3, 2.4.0-2.4.2, 2.5.0, or 2.6.0
-
Confirm TensorFlow Lite usageCheck if the code imports tflite or tflite_runtime with 'python -c "import tflite_runtime as tflite; print(tflite.__version__)"' or check if models use .tflite formatAffected if TensorFlow Lite interpreter or .tflite models are in use
-
Identify pooling operation usageInspect model files or code for pooling operations: search for 'AvgPool', 'MaxPool', 'average_pooling2d', 'max_pooling2d', or examine tflite models using tools like Netron or tflite_inspectorAffected if Models contain pooling operations (kAvgPool, kMaxPool) in the TFLite graph
-
Verify TFLite interpreter implementationCheck if the application uses tf.lite.Interpreter to run inference on models, which executes the vulnerable pooling code pathsAffected if Code uses tf.lite.Interpreter or tflite_runtime.Interpreter for inference
You are affected if you run TensorFlow versions 2.3.0-2.3.3, 2.4.0-2.4.2, 2.5.0, or 2.6.0 AND use TensorFlow Lite to execute models containing pooling operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.3.42.4.3
Update TensorFlow to version 2.6.0 or the patched versions (2.5.1, 2.4.3, 2.3.4) which include the fix for the missing divisor validation in pooling implementations.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data