[Snyk] Fix for 7 vulnerabilities

[tim-s-ccs]

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-dev.txt

⚠️ Warning

Werkzeug 2.2.3 has requirement MarkupSafe>=2.1.1, but you have MarkupSafe 1.1.1.
Flask 2.2.5 has requirement itsdangerous>=2.0, but you have itsdangerous 1.1.0.
Flask 2.2.5 has requirement click>=8.0, but you have click 7.1.2.
Flask 2.2.5 has requirement Jinja2>=3.0, but you have Jinja2 2.11.3.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	704/1000 Why? Has a fix available, CVSS 9.8	Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047	certifi: 2022.12.7 -> 2023.7.22	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Information Exposure SNYK-PYTHON-FLASK-5490129	flask: 1.1.4 -> 2.2.5	No	No Known Exploit
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Exposure of Data Element to Wrong Session SNYK-PYTHON-REDIS-5291195	redis: 4.5.1 -> 4.5.4	No	Proof of Concept
	429/1000 Why? Has a fix available, CVSS 4.3	Exposure of Data Element to Wrong Session SNYK-PYTHON-REDIS-5291196	redis: 4.5.1 -> 4.5.4	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Information Exposure SNYK-PYTHON-REQUESTS-5595532	requests: 2.28.2 -> 2.31.0	No	No Known Exploit
	344/1000 Why? Has a fix available, CVSS 2.6	Access Restriction Bypass SNYK-PYTHON-WERKZEUG-3319935	werkzeug: 1.0.1 -> 2.2.3	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-WERKZEUG-3319936	werkzeug: 1.0.1 -> 2.2.3	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:

🦉 Access Restriction Bypass
🦉 Denial of Service (DoS)