Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Security upgrade tensorflow from 1.13.1 to 2.10.1 #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade tensorflow from 1.13.1 to 2.10.1 #29

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • requirements.txt
⚠️ Warning 
Sphinx 1.8.6 has requirement docutils<0.18,>=0.11, but you have docutils 0.18.1.
pyasn1-modules 0.2.8 has requirement pyasn1<0.5.0,>=0.4.6, but you have pyasn1 0.4.2.
google-auth 1.35.0 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.
google-api-core 1.32.0 has requirement protobuf<3.18.0,>=3.12.0; python_version < "3", but you have protobuf 3.6.1.
google-api-core 1.32.0 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136192		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136196		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136200		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1		 Out-of-bounds Write
SNYK-PYTHON-TENSORFLOW-3136204		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136208		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136212		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
medium severity 516/1000
Why? Recently disclosed, Has a fix available, CVSS 4.6		 Buffer Overflow
SNYK-PYTHON-TENSORFLOW-3136216		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-3136220		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136224		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136228		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136232		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-3136236		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Reachable Assertion
SNYK-PYTHON-TENSORFLOW-3136240		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136244		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
medium severity 526/1000
Why? Recently disclosed, Has a fix available, CVSS 4.8		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3136248		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Improper Input Validation
SNYK-PYTHON-TENSORFLOW-3136252		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Incorrect Calculation of Buffer Size
SNYK-PYTHON-TENSORFLOW-3136256		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Buffer Overflow
SNYK-PYTHON-TENSORFLOW-3136260		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
medium severity 626/1000
Why? Recently disclosed, Has a fix available, CVSS 6.8		 Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-3136264		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
medium severity 526/1000
Why? Recently disclosed, Has a fix available, CVSS 4.8		 Incorrect Calculation of Buffer Size
SNYK-PYTHON-TENSORFLOW-3136268		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Buffer Overflow
SNYK-PYTHON-TENSORFLOW-3136272		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6		 Always-Incorrect Control Flow Implementation
SNYK-PYTHON-TENSORFLOW-3136276		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit
medium severity 626/1000
Why? Recently disclosed, Has a fix available, CVSS 6.8		 Out-of-Bounds
SNYK-PYTHON-TENSORFLOW-3136280		 tensorflow:
1.13.1 -> 2.10.1
No No Known Exploit

(*) 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

@snyk-bot
fix: requirements.txt to reduce vulnerabilities
710c929 
The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136192
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136196
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136200
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136204
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136208
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136212
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136216
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136220
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136224
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136228
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136232
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136236
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136240
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136244
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136248
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136252
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136256
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136260
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136264
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136268
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136272
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136276
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3136280
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@snyk-bot