Skip to content

TensorFlow has segmentation fault in tfg-translate

High severity GitHub Reviewed Published Mar 24, 2023 in tensorflow/tensorflow • Updated Mar 31, 2023

Package

pip tensorflow (pip)

Affected versions

< 2.11.1

Patched versions

2.11.1
pip tensorflow-cpu (pip)
< 2.11.1
2.11.1

Description

Impact

Out-of-bounds access due to mismatched integer type sizes in ValueMap::Manager::GetValueOrCreatePlaceholder. Bug with tfg-translate call to InitMlir. The problem happens with generic functions, as it is already handled for non-generic functions. This is because they, unlike non-generic functions, are using the "old importer". A better long-term solution may be to have the "new importer" handle generic functions.

Patches

We have patched the issue in GitHub

The fix will be included in TensorFlow 2.12.0. We will also cherrypick this commit on TensorFlow 2.11.1

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by r3pwnx

Affiliation

360 AIVul

References

@pak-laura pak-laura published to tensorflow/tensorflow Mar 24, 2023
Published to the GitHub Advisory Database Mar 24, 2023
Reviewed Mar 24, 2023
Published by the National Vulnerability Database Mar 25, 2023
Last updated Mar 31, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.106%
(44th percentile)

Weaknesses

CVE ID

CVE-2023-25671

GHSA ID

GHSA-j5w9-hmfh-4cr6

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.