This repository has been archived by the owner on Jun 27, 2023. It is now read-only.
[Snyk] Security upgrade tensorflow from 1.14.0 to 2.6.4 #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841370
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841375
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841380
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841384
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841388
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841392
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841396
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841400
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841404
tensorflow:
1.14.0 -> 2.6.4
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.8
SNYK-PYTHON-TENSORFLOW-2841408
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841412
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 4.7
SNYK-PYTHON-TENSORFLOW-2841416
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 7.1
SNYK-PYTHON-TENSORFLOW-2841420
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841424
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841428
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841436
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841439
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841443
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841446
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 7.5
SNYK-PYTHON-TENSORFLOW-2841453
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841459
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 7.5
SNYK-PYTHON-TENSORFLOW-2841463
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841468
tensorflow:
1.14.0 -> 2.6.4
Why? Recently disclosed, Has a fix available, CVSS 5.5
SNYK-PYTHON-TENSORFLOW-2841472
tensorflow:
1.14.0 -> 2.6.4
(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Remote Code Execution (RCE)