Tensorflow
Approved changes feed: RSS · Atom
cpe:2.3:a:google:tensorflow:2.10.0:*:*:*:*:*:*:*
part: a version: 2.10.0 update: *
| Vendor | Google (f181d1eb-7269-5bae-b76e-e66ceb214562) |
|---|---|
| Product | Tensorflow (b00eb799-7f6b-5a1c-af79-6e563231bc87) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-41911 |
vulnerable | 2026-06-08 05:49:28.848771 |
Invalid char to bool conversion when printing a tensor in Tensorflow
MEDIUM (4.8)
TensorFlow is an open source platform for machine learning. When printing a tensor, we get it's data as a `const char*` array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from `char` to `bool` are undefined if the `char` is not `0` or `1`, so sanitizers/fuzzers will crash. The issue has been patched in GitHub commit `1be74370327`. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.10.1, TensorFlow 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Published: 2022-11-18T00:00:00.000Z
Updated: 2025-04-23T16:36:49.951Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41909 |
vulnerable | 2026-06-08 05:49:28.847491 |
Segfault in `CompositeTensorVariantToComponents` in Tensorflow
MEDIUM (4.8)
TensorFlow is an open source platform for machine learning. An input `encoded` that is not a valid `CompositeTensorVariant` tensor will trigger a segfault in `tf.raw_ops.CompositeTensorVariantToComponents`. We have patched the issue in GitHub commits bf594d08d377dc6a3354d9fdb494b32d45f91971 and 660ce5a89eb6766834bdc303d2ab3902aef99d3d. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Published: 2022-11-18T00:00:00.000Z
Updated: 2025-04-22T16:02:49.290Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41908 |
vulnerable | 2026-06-08 05:49:28.846812 |
`CHECK` fail via inputs in `PyFunc` in Tensorflow
MEDIUM (4.8)
TensorFlow is an open source platform for machine learning. An input `token` that is not a UTF-8 bytestring will trigger a `CHECK` fail in `tf.raw_ops.PyFunc`. We have patched the issue in GitHub commit 9f03a9d3bafe902c1e6beb105b2f24172f238645. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Published: 2022-11-18T00:00:00.000Z
Updated: 2025-04-22T16:02:59.540Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41900 |
vulnerable | 2026-06-08 05:49:28.829599 |
FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow
HIGH (7.1)
TensorFlow is an open source platform for machine learning. The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution. We have patched the issue in GitHub commit 216525144ee7c910296f5b05d214ca1327c9ce48. The fix will be included in TensorFlow 2.11.0. We will also cherry pick this commit on TensorFlow 2.10.1.
Published: 2022-11-18T00:00:00.000Z
Updated: 2025-04-22T16:03:33.028Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41899 |
vulnerable | 2026-06-08 05:49:28.829064 |
`CHECK` fail via inputs in `SdcaOptimizer` in Tensorflow
MEDIUM (4.8)
TensorFlow is an open source platform for machine learning. Inputs `dense_features` or `example_state_data` not of rank 2 will trigger a `CHECK` fail in `SdcaOptimizer`. We have patched the issue in GitHub commit 80ff197d03db2a70c6a111f97dcdacad1b0babfa. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Published: 2022-11-18T00:00:00.000Z
Updated: 2025-04-22T16:03:45.167Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41887 |
vulnerable | 2026-06-08 05:49:28.810464 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41886 |
vulnerable | 2026-06-08 05:49:28.809892 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41884 |
vulnerable | 2026-06-08 05:49:28.808191 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41880 |
vulnerable | 2026-06-08 05:49:28.797600 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.