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 urllib3 from 1.7.1 to 1.26.5 #5

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 7, 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:
    • dev-requirements.txt
⚠️ Warning
httpretty 0.8.3 has requirement urllib3==1.7.1, but you have urllib3 1.26.7.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 599/1000
Why? Has a fix available, CVSS 7.7
HTTP Header Injection
SNYK-PYTHON-URLLIB3-1014645
urllib3:
1.7.1 -> 1.26.5
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Insecure Defaults
SNYK-PYTHON-URLLIB3-1047466
urllib3:
1.7.1 -> 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.7.1 -> 1.26.5
No No Known Exploit
high severity 794/1000
Why? Mature exploit, Has a fix available, CVSS 7.3
CRLF injection
SNYK-PYTHON-URLLIB3-174323
urllib3:
1.7.1 -> 1.26.5
No Mature
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Improper Certificate Validation
SNYK-PYTHON-URLLIB3-174464
urllib3:
1.7.1 -> 1.26.5
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Authentication Bypass
SNYK-PYTHON-URLLIB3-72681
urllib3:
1.7.1 -> 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 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