Skip to content

[Snyk] Fix for 12 vulnerabilities - #5

Open
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-399f6a0eac69409d6d769bf23cfe2673
Open

[Snyk] Fix for 12 vulnerabilities#5
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-399f6a0eac69409d6d769bf23cfe2673

Conversation

@snyk-bot

Copy link
Copy Markdown

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
oauth2client 4.1.1 requires rsa, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Issue Upgrade Breaking Change Exploit Maturity
high severity Improper Input Validation
SNYK-PYTHON-FLASK-42185
flask:
0.12.2 -> 0.12.3
No No Known Exploit
high severity Denial of Service (DoS)
SNYK-PYTHON-FLASK-451637
flask:
0.12.2 -> 0.12.3
No No Known Exploit
medium severity CRLF Injection
SNYK-PYTHON-HTTPLIB2-569758
httplib2:
0.10.3 -> 0.18.0
No No Known Exploit
high severity CRLF Injection
SNYK-PYTHON-HTTPLIB2-570767
httplib2:
0.10.3 -> 0.18.0
No No Known Exploit
medium severity Sandbox Escape
SNYK-PYTHON-JINJA2-174126
Jinja2:
2.9.6 -> 2.10.1
No No Known Exploit
medium severity Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-72651
lxml:
3.6.0 -> 4.2.5
No No Known Exploit
high severity Information Exposure
SNYK-PYTHON-REQUESTS-72435
requests:
2.17.3 -> 2.20
No No Known Exploit
medium severity Access Restriction Bypass
SNYK-PYTHON-RSA-570831
rsa:
3.4.2 -> 4.1
No No Known Exploit
high severity CRLF injection
SNYK-PYTHON-URLLIB3-174323
urllib3:
1.21.1 -> 1.24.3
No Mature
high severity Improper Certificate Validation
SNYK-PYTHON-URLLIB3-174464
urllib3:
1.21.1 -> 1.24.3
No No Known Exploit
medium severity Authentication Bypass
SNYK-PYTHON-URLLIB3-72681
urllib3:
1.21.1 -> 1.24.3
No No Known Exploit
high severity Insufficient Randomness
SNYK-PYTHON-WERKZEUG-458931
Werkzeug:
0.12.2 -> 0.15.3
werkzeug:
0.12.2 -> 0.15.3
No No Known Exploit

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