[Snyk] Fix for 6 vulnerabilities

[MarcelRaschke]

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

scipy 1.1.0 requires numpy, which is not installed.
scikit-optimize 0.5.2 requires numpy, which is not installed.
requests 2.20.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 1.26.5.
requests-cache 0.9.6 has requirement requests>=2.22, but you have requests 2.20.0.
python-telegram-bot 11.1.0 requires cryptography, which is not installed.
pytest-cov 2.6.0 requires coverage, which is not installed.
pandas 0.23.4 requires numpy, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	811/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.8	Information Exposure SNYK-PYTHON-REQUESTS-72435	requests: 2.19.1 -> 2.20	No	Proof of Concept
	599/1000 Why? Has a fix available, CVSS 7.7	HTTP Header Injection SNYK-PYTHON-URLLIB3-1014645	urllib3: 1.22 -> 1.26.5	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-URLLIB3-1533435	urllib3: 1.22 -> 1.26.5	No	No Known Exploit
	794/1000 Why? Mature exploit, Has a fix available, CVSS 7.3	CRLF injection SNYK-PYTHON-URLLIB3-174323	urllib3: 1.22 -> 1.26.5	No	Mature
	589/1000 Why? Has a fix available, CVSS 7.5	Improper Certificate Validation SNYK-PYTHON-URLLIB3-174464	urllib3: 1.22 -> 1.26.5	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Authentication Bypass SNYK-PYTHON-URLLIB3-72681	urllib3: 1.22 -> 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)
🦉 CRLF injection