doc-ai / tensorio-ios

Tensor/IO for iOS, with support for on-device inference and training with TensorFlow and TensorFlow Lite
Other
31 stars 10 forks source link

CVE-2019-16778 (High) detected in TensorIOTensorFlow-0.3.0 #185

Closed mend-for-github-com[bot] closed 4 years ago

mend-for-github-com[bot] commented 4 years ago

CVE-2019-16778 - High Severity Vulnerability

Vulnerable Library - TensorIOTensorFlow-0.3.0

An unofficial build of TensorFlow for iOS used by TensorIO, supporting inference, evaluation, and training.

Library home page: https://storage.googleapis.com/tensorio-build/TensorIO-TensorFlow-1.13_0.3.0.tar.gz

Path to dependency file: /tmp/ws-scm/tensorio-ios/SwiftTensorFlowExample/Podfile.lock

Path to vulnerable library: /tmp/ws-scm/tensorio-ios/SwiftTensorFlowExample/Podfile.lock,/tmp/ws-scm/tensorio-ios/TensorFlowExample/Podfile.lock

Dependency Hierarchy: - TensorIO/TensorFlow-0.9.7 (Root Library) - :x: **TensorIOTensorFlow-0.3.0** (Vulnerable Library)

Found in HEAD commit: 1734926baf16d6aceab0aa13e2b0def236b1a583

Vulnerability Details

In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.

Publish Date: 2019-12-16

URL: CVE-2019-16778

CVSS 3 Score Details (9.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16778

Release Date: 2019-12-16

Fix Resolution: tensorflow - 1.15.0

phildow commented 4 years ago

Will be resolved with attempted update to TF 1.15

phildow commented 4 years ago

Updated to TF 1.15 build, let's see if that addresses this issue. If not we'll try again with TF 2.0