Google Tensorflow up to 2.5.2/2.6.2/2.7.0 Initialize memory leak

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.2$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Tensorflow up to 2.5.2/2.6.2/2.7.0. It has been declared as problematic. This vulnerability affects the function ImmutableExecutorState::Initialize. Such manipulation leads to memory leak. This vulnerability is listed as CVE-2022-23578. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Tensorflow up to 2.5.2/2.6.2/2.7.0 (Artificial Intelligence Software). It has been rated as problematic. Affected by this issue is the function ImmutableExecutorState::Initialize. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability.

The weakness was presented 02/05/2022 as GHSA-8r7c-3cm2-3h8f. The advisory is available at github.com. This vulnerability is handled as CVE-2022-23578 since 01/19/2022. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 2.5.3, 2.6.3, 2.7.1 or 2.8.0 eliminates this vulnerability. Applying the patch c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd 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 best quality of vulnerability data, you may have to visit 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.3
VulDB Meta Temp Score: 4.2

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

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

CVSSv2info

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

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

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
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.5.3/2.6.3/2.7.1/2.8.0
Patch: c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd

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-8r7c-3cm2-3h8f
Status: Confirmed

CVE: CVE-2022-23578 (🔍)
GCVE (CVE): GCVE-0-2022-23578
GCVE (VulDB): GCVE-100-192338

Entryinfo

Created: 02/05/2022 08:21
Updated: 02/07/2022 10:12
Changes: 02/05/2022 08:21 (53), 02/07/2022 10:12 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit 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!