8000 [Snyk] Fix for 5 vulnerabilities by XadillaX · Pull Request #9 · XadillaX/TimelineJS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Snyk] Fix for 5 vulnerabilities #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and th 8000 e 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

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

Conversation

XadillaX
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


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 539/1000
Why? Has a fix available, CVSS 6.5
Arbitrary Code Execution
SNYK-PYTHON-BOTO-40479
boto:
2.13.3 -> 2.39.0
No No Known Exploit
medium severity 540/1000
Why? Has a fix available, CVSS 6.3
Race Condition
SNYK-PYTHON-PARAMIKO-2429583
paramiko:
1.10.1 -> 2.10.1
No No Known Exploit
critical severity 811/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
Authentication Bypass
SNYK-PYTHON-PARAMIKO-42086
paramiko:
1.10.1 -> 2.10.1
No Proof of Concept
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Authentication Bypass
SNYK-PYTHON-PARAMIKO-455391
paramiko:
1.10.1 -> 2.10.1
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Information Exposure
SNYK-PYTHON-PYCRYPTO-40008
pycrypto:
2.6 -> 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


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Arbitrary Code Execution

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.

2 participants
0