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.5.3 #36

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Feb 7, 2022

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
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Integer Overflow or Wraparound
SNYK-PYTHON-TENSORFLOW-2395421
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-2395424
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-2395427
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-2395430
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-Bound
SNYK-PYTHON-TENSORFLOW-2395433
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Write
SNYK-PYTHON-TENSORFLOW-2395436
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-2395439
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-2395442
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-2395445
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-2395448
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
high severity 666/1000
Why? Recently disclosed, Has a fix available, CVSS 7.6
Integer Overflow or Wraparound
SNYK-PYTHON-TENSORFLOW-2395451
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
high severity 666/1000
Why? Recently disclosed, Has a fix available, CVSS 7.6
Use of Uninitialized Resource
SNYK-PYTHON-TENSORFLOW-2395454
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
medium severity 501/1000
Why? Recently disclosed, Has a fix available, CVSS 4.3
Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-2395457
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
high severity 641/1000
Why? Recently disclosed, Has a fix available, CVSS 7.1
Race Condition
SNYK-PYTHON-TENSORFLOW-2395461
tensorflow:
1.2.1 -> 2.5.3
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Write
SNYK-PYTHON-TENSORFLOW-2395464
tensorflow:
1.2.1 -> 2.5.3
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

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