PyPi: Tensorflow-Rocm

CVE-2020-15196

Safety vulnerability ID: 57992

This vulnerability was reviewed by experts

The information on this page was manually curated by our Cybersecurity Intelligence Team.

Created at Sep 25, 2020 Updated at Nov 29, 2024
Scan your Python projects for vulnerabilities →

Advisory

Tensorflow-rocm version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the "SparseCountSparseOutput" and "RaggedCountSparseOutput" implementations don't validate that the "weights" tensor has the same shape as the data. The check exists for "DenseCountSparseOutput", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02.
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph

Affected package

tensorflow-rocm

Latest version: 2.14.0.600

TensorFlow is an open source machine learning framework for everyone.

Affected versions

Fixed versions

Vulnerability changelog

This vulnerability has no description

Resources

Use this package?

Scan your Python project for dependency vulnerabilities in two minutes

Scan your application

Severity Details

CVSS Base Score

CRITICAL 9.9

CVSS v3 Details

CRITICAL 9.9
Attack Vector (AV)
NETWORK
Attack Complexity (AC)
LOW
Privileges Required (PR)
LOW
User Interaction (UI)
NONE
Scope (S)
CHANGED
Confidentiality Impact (C)
HIGH
Integrity Impact (I)
HIGH
Availability Availability (A)
HIGH

CVSS v2 Details

MEDIUM 6.5
Access Vector (AV)
NETWORK
Access Complexity (AC)
LOW
Authentication (Au)
SINGLE
Confidentiality Impact (C)
PARTIAL
Integrity Impact (I)
PARTIAL
Availability Impact (A)
PARTIAL