Google Tensorflow up to 2.7.0 StatusOr 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.
4.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Tensorflow up to 2.7.0. It has been classified as problematic. This affects an unknown function. The manipulation of the argument StatusOr leads to unusual condition. This vulnerability is referenced as CVE-2022-23590. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Google Tensorflow up to 2.7.0 (Artificial Intelligence Software). It has been rated as problematic. This issue affects an unknown code block. The manipulation of the argument StatusOr with an unknown input leads to a unusual condition vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability.

The weakness was published 02/05/2022 as GHSA-pqrv-8r2f-7278. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-23590 since 01/19/2022. Technical details are known, but no exploit is available.

Upgrading to version 2.7.1 or 2.8.0 eliminates this vulnerability. Applying the patch 955059813cc325dc1db5e2daa6221271406d4439 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: 4.8
VulDB Meta Temp Score: 4.7

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.9
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.7.1/2.8.0
Patch: 955059813cc325dc1db5e2daa6221271406d4439

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-pqrv-8r2f-7278
Status: Confirmed

CVE: CVE-2022-23590 (🔍)
GCVE (CVE): GCVE-0-2022-23590
GCVE (VulDB): GCVE-100-192365

Entryinfo

Created: 02/05/2022 08:49
Updated: 02/07/2022 13:20
Changes: 02/05/2022 08:49 (53), 02/07/2022 13:20 (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 need the next level of professionalism?

Upgrade your account now!