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 10 vulnerabilities #364

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

Conversation

Bento007
Copy link
Member

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
⚠️ Warning
requests 2.22.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5.
hca 6.4.0 has requirement dcplib<3,>=2.0.2, but you have dcplib 3.12.0.
hca 6.4.0 has requirement cryptography==2.3.1, but you have cryptography 3.2.
hca 6.4.0 has requirement rsa<=3.5.0,>=3.1.2, but you have rsa 4.7.
dcplib 3.12.0 has requirement cryptography<3,>=2.3, but you have cryptography 3.2.
botocore 1.12.42 has requirement urllib3<1.25,>=1.20; python_version >= "3.4", but you have urllib3 1.26.5.
boto3 1.9.42 has requirement s3transfer<0.2.0,>=0.1.10, but you have s3transfer 0.2.1.
awscli 1.16.52 has requirement PyYAML<=3.13,>=3.10, but you have PyYAML 5.4.
awscli 1.16.52 has requirement rsa<=3.5.0,>=3.1.2, but you have rsa 4.7.
awscli 1.16.52 has requirement s3transfer<0.2.0,>=0.1.12, but you have s3transfer 0.2.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Timing Attack
SNYK-PYTHON-CRYPTOGRAPHY-1022152
cryptography:
2.3.1 -> 3.2
No No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-JINJA2-1012994
jinja2:
2.10.3 -> 2.11.3
No Proof of Concept
high severity 691/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
Use of a Broken or Risky Cryptographic Algorithm
SNYK-PYTHON-PYJWT-2840625
pyjwt:
1.7.1 -> 2.4.0
No Proof of Concept
critical severity 876/1000
Why? Mature exploit, Has a fix available, CVSS 9.8
Improper Access Control
SNYK-PYTHON-PYYAML-550022
pyyaml:
5.1.1 -> 5.4
No Mature
critical severity 704/1000
Why? Has a fix available, CVSS 9.8
Arbitrary Code Execution
SNYK-PYTHON-PYYAML-559098
pyyaml:
5.1.1 -> 5.4
No No Known Exploit
critical severity 876/1000
Why? Mature exploit, Has a fix available, CVSS 9.8
Arbitrary Code Execution
SNYK-PYTHON-PYYAML-590151
pyyaml:
5.1.1 -> 5.4
No Mature
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Timing Attack
SNYK-PYTHON-RSA-1038401
rsa:
3.4.2 -> 4.7
No No Known Exploit
medium severity 494/1000
Why? Has a fix available, CVSS 5.6
Access Restriction Bypass
SNYK-PYTHON-RSA-570831
rsa:
3.4.2 -> 4.7
No No Known Exploit
high severity 599/1000
Why? Has a fix available, CVSS 7.7
HTTP Header Injection
SNYK-PYTHON-URLLIB3-1014645
urllib3:
1.24.3 -> 1.26.5
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-URLLIB3-1533435
urllib3:
1.24.3 -> 1.26.5
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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Improper Access Control
🦉 More lessons are available in Snyk Learn

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.

None yet

2 participants