Heap buffer overflow in `QuantizedResizeBilinear`GHSA-8c89-2vwr-chcq
LOWFix: tensorflow/tensorflow@f6c40f0GHSA-8c89-2vwr-chcq is a low-severity (CVSS 2.5) CWE-131 vulnerability in tensorflow. 1 public exploit reference exists, so weaponization risk is real. A fix is available for tensorflow — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-8c89-2vwr-chcq by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
tensorflow🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu+4 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
An attacker can cause a heap buffer overflow in QuantizedResizeBilinear by passing in invalid thresholds for the quantization:
import tensorflow as tf
images = tf.constant([], shape=[0], dtype=tf.qint32)
size = tf.constant([], shape=[0], dtype=tf.int32)
min = tf.constant([], dtype=tf.float32)
max = tf.constant([], dtype=tf.float32)
tf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max, align_corners=False, half_pixel_centers=False)
This is because the implementation assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:
const float in_min = context->input(2).flat<float>()(0);
const float in_max = context->input(3).flat<float>()(0);
However, if any of these tensors is empty, then .flat<T>() is an empty buffer and accessing the element at position 0 results in overflow.
Patches
We have patched the issue in GitHub commit f6c40f0c6cbf00d46c7717a26419f2062f2f8694.
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | tensorflow | all versions | 2.1.4pip install --upgrade 'tensorflow==2.1.4' |
| 🐍PyPI | tensorflow | ≥ 2.2.0&&< 2.2.3 | 2.2.3pip install --upgrade 'tensorflow==2.2.3' |
| 🐍PyPI | tensorflow | ≥ 2.3.0&&< 2.3.3 | 2.3.3pip install --upgrade 'tensorflow==2.3.3' |
| 🐍PyPI | tensorflow | ≥ 2.4.0&&< 2.4.2 | 2.4.2pip install --upgrade 'tensorflow==2.4.2' |
| 🐍PyPI | tensorflow-cpu | all versions | 2.1.4pip install --upgrade 'tensorflow-cpu==2.1.4' |
| 🐍PyPI | tensorflow-cpu | ≥ 2.2.0&&< 2.2.3 | 2.2.3pip install --upgrade 'tensorflow-cpu==2.2.3' |
Affected Products
tensorflowgoogleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tensorflow to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c89-2vwr-chcq is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is GHSA-8c89-2vwr-chcq in your dependencies?
Find it across PyPI, including transitive dependencies.