Skip to content

`FractionalMaxPoolGrad` Heap out of bounds read

Moderate severity GitHub Reviewed Published Nov 18, 2022 in tensorflow/tensorflow • Updated Feb 1, 2023

Package

pip tensorflow (pip)

Affected versions

< 2.8.4
>= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1

Patched versions

2.8.4
2.9.3
2.10.1
pip tensorflow-cpu (pip)
< 2.8.4
>= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1
2.8.4
2.9.3
2.10.1
pip tensorflow-gpu (pip)
< 2.8.4
>= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1
2.8.4
2.9.3
2.10.1

Description

Impact

If FractionMaxPoolGrad is given outsize inputs row_pooling_sequence and col_pooling_sequence, TensorFlow will crash.

import tensorflow as tf
tf.raw_ops.FractionMaxPoolGrad(
	orig_input = [[[[1, 1, 1, 1, 1]]]],
    orig_output = [[[[1, 1, 1]]]],
    out_backprop = [[[[3], [3], [6]]]],
    row_pooling_sequence = [-0x4000000, 1, 1], 
    col_pooling_sequence = [-0x4000000, 1, 1], 
    overlapping = False
 )

Patches

We have patched the issue in GitHub commit d71090c3e5ca325bdf4b02eb236cfb3ee823e927.

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.

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 Vul AI.

References

@pak-laura pak-laura published to tensorflow/tensorflow Nov 18, 2022
Published by the National Vulnerability Database Nov 18, 2022
Published to the GitHub Advisory Database Nov 21, 2022
Reviewed Nov 21, 2022
Last updated Feb 1, 2023

Severity

Moderate

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
High
Privileges required
Low
User interaction
Required
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:H/PR:L/UI:R/S:U/C:N/I:N/A:H

EPSS score

0.111%
(45th percentile)

Weaknesses

CVE ID

CVE-2022-41897

GHSA ID

GHSA-f2w8-jw48-fr7j

Source code

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