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.10.1 #28
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 2.6
SNYK-PYTHON-TENSORFLOW-3136192
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136196
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136200
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 7.1
SNYK-PYTHON-TENSORFLOW-3136204
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136208
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136212
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 4.6
SNYK-PYTHON-TENSORFLOW-3136216
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136220
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136224
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136228
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136232
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136236
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136240
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136244
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 4.8
SNYK-PYTHON-TENSORFLOW-3136248
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136252
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136256
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136260
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 6.8
SNYK-PYTHON-TENSORFLOW-3136264
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 4.8
SNYK-PYTHON-TENSORFLOW-3136268
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136272
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 2.6
SNYK-PYTHON-TENSORFLOW-3136276
tensorflow:
1.14.0 -> 2.10.1
Why? Recently disclosed, Has a fix available, CVSS 6.8
SNYK-PYTHON-TENSORFLOW-3136280
tensorflow:
1.14.0 -> 2.10.1
(*) 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 affected 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:
🦉 Denial of Service (DoS)
🦉 Denial of Service (DoS)
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn