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] Fix for 6 vulnerabilities #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
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
github3.py 0.9.3 requires uritemplate.py, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 540/1000
Why? Has a fix available, CVSS 6.3
Race Condition
SNYK-PYTHON-PARAMIKO-2429583
paramiko:
1.15.1 -> 2.10.1
No No Known Exploit
critical severity 876/1000
Why? Mature exploit, Has a fix available, CVSS 9.8
Authentication Bypass
SNYK-PYTHON-PARAMIKO-42086
paramiko:
1.15.1 -> 2.10.1
No Mature
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Authentication Bypass
SNYK-PYTHON-PARAMIKO-455391
paramiko:
1.15.1 -> 2.10.1
No No Known Exploit
medium severity 529/1000
Why? Has a fix available, CVSS 6.3
Session Fixation
SNYK-PYTHON-REQUESTS-40316
requests:
2.3.0 -> 2.20
No No Known Exploit
critical severity 811/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
Information Exposure
SNYK-PYTHON-REQUESTS-72435
requests:
2.3.0 -> 2.20
No Proof of Concept
high severity 604/1000
Why? Has a fix available, CVSS 7.8
SQL Injection
SNYK-PYTHON-SQLALCHEMY-173678
sqlalchemy:
0.9.7 -> 1.2.18
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:

🦉 Authentication Bypass
🦉 SQL Injection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant