Google TensorFlow up to 2.8.3/2.9.2/2.10.0 ThreadUnsafeUnigramCandidateSampler denial of service

Summaryinfo

A vulnerability identified as problematic has been detected in Google TensorFlow up to 2.8.3/2.9.2/2.10.0. The impacted element is the function ThreadUnsafeUnigramCandidateSampler. Performing a manipulation results in denial of service. This vulnerability is reported as CVE-2022-41896. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Google TensorFlow up to 2.8.3/2.9.2/2.10.0 (Artificial Intelligence Software). This affects the function ThreadUnsafeUnigramCandidateSampler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:

TensorFlow is an open source platform for machine learning. If `ThreadUnsafeUnigramCandidateSampler` is given input `filterbank_channel_count` greater than the allowed max size, TensorFlow will crash. We have patched the issue in GitHub commit 39ec7eaf1428e90c37787e5b3fbd68ebd3c48860. 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.

The weakness was disclosed 11/19/2022 as GHSA-rmg2-f698-wq35. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-41896 since 09/30/2022. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 2.8.4, 2.9.3, 2.10.1 or 2.11 eliminates this vulnerability. Applying the patch 39ec7eaf1428e90c37787e5b3fbd68ebd3c48860 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• Google

Name

• TensorFlow

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.8.0
• 2.8.1
• 2.8.2
• 2.8.3
• 2.9
• 2.9.0
• 2.9.1
• 2.9.2
• 2.10.0

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion