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.

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

[Snyk] Security upgrade tensorflow from 1.2.1 to 2.6.1 #27

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Nov 8, 2021

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

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912554
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912557
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912560
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912561
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Out-of-Bounds
SNYK-PYTHON-TENSORFLOW-1912566
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912569
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912573
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Out-of-Bounds
SNYK-PYTHON-TENSORFLOW-1912576
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Buffer Overflow
SNYK-PYTHON-TENSORFLOW-1912579
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Buffer Overflow
SNYK-PYTHON-TENSORFLOW-1912583
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Heap-based Buffer Overflow
SNYK-PYTHON-TENSORFLOW-1912586
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-1912589
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Out-of-Bounds
SNYK-PYTHON-TENSORFLOW-1912592
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 676/1000
Why? Recently disclosed, Has a fix available, CVSS 7.8
Use of Uninitialized Variable
SNYK-PYTHON-TENSORFLOW-1912596
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-1912600
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912603
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 676/1000
Why? Recently disclosed, Has a fix available, CVSS 7.8
Access of Uninitialized Pointer
SNYK-PYTHON-TENSORFLOW-1912606
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 668/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912609
tensorflow:
1.2.1 -> 2.6.1
No Proof of Concept
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Deserialization of Untrusted Data
SNYK-PYTHON-TENSORFLOW-1912615
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 676/1000
Why? Recently disclosed, Has a fix available, CVSS 7.8
Use After Free
SNYK-PYTHON-TENSORFLOW-1912619
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 676/1000
Why? Recently disclosed, Has a fix available, CVSS 7.8
Heap-based Buffer Overflow
SNYK-PYTHON-TENSORFLOW-1912622
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 676/1000
Why? Recently disclosed, Has a fix available, CVSS 7.8
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912625
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912628
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Improper Input Validation
SNYK-PYTHON-TENSORFLOW-1912631
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 616/1000
Why? Recently disclosed, Has a fix available, CVSS 6.6
Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-1912634
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912637
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912640
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Use of Uninitialized Variable
SNYK-PYTHON-TENSORFLOW-1912643
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Divide By Zero
SNYK-PYTHON-TENSORFLOW-1912646
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Buffer Overflow
SNYK-PYTHON-TENSORFLOW-1912649
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Remote Code Execution (RCE)
SNYK-PYTHON-TENSORFLOW-1912653
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Remote Code Execution (RCE)
SNYK-PYTHON-TENSORFLOW-1912656
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Remote Code Execution (RCE)
SNYK-PYTHON-TENSORFLOW-1912659
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 636/1000
Why? Recently disclosed, Has a fix available, CVSS 7
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912662
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 636/1000
Why? Recently disclosed, Has a fix available, CVSS 7
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912665
tensorflow:
1.2.1 -> 2.6.1
No No Known Exploit
high severity 636/1000
Why? Recently disclosed, Has a fix available, CVSS 7
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-1912668
tensorflow:
1.2.1 -> 2.6.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 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

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912554
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912557
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912560
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912561
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912566
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912569
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912573
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912576
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912579
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912583
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912586
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912589
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912592
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912596
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912600
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912603
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912606
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912609
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912615
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912619
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912622
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912625
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912628
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912631
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912634
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912637
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912640
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912643
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912646
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912649
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912653
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912656
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912659
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912662
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912665
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-1912668
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant