Google Tensorflow up to 2.6.2/2.7.0 unusual condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Google Tensorflow up to 2.6.2/2.7.0. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in unusual condition. This vulnerability is reported as CVE-2022-23572. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Google Tensorflow up to 2.6.2/2.7.0 (Artificial Intelligence Software). This affects an unknown code. The manipulation with an unknown input leads to a unusual condition vulnerability. CWE is classifying the issue as CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. This is going to have an impact on availability.

The weakness was disclosed 02/05/2022 as GHSA-rww7-2gpw-fv6j. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-23572 since 01/19/2022. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.6.3, 2.7.1 or 2.8.0 eliminates this vulnerability. Applying the patch cb164786dc891ea11d3a900e90367c339305dc7b 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

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Unusual condition
CWE: CWE-754
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Tensorflow 2.6.3/2.7.1/2.8.0
Patch: cb164786dc891ea11d3a900e90367c339305dc7b

Timelineinfo

01/19/2022 🔍
02/05/2022 +17 days 🔍
02/05/2022 +0 days 🔍
02/07/2022 +2 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: GHSA-rww7-2gpw-fv6j
Status: Confirmed

CVE: CVE-2022-23572 (🔍)
GCVE (CVE): GCVE-0-2022-23572
GCVE (VulDB): GCVE-100-192357

Entryinfo

Created: 02/05/2022 08:42
Updated: 02/07/2022 12:23
Changes: 02/05/2022 08:42 (51), 02/07/2022 12:23 (1)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!