[Snyk] Fix for 6 vulnerabilities

[amymariparker]

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

quart 0.18.4 requires hypercorn, which is not installed.
quart 0.18.4 requires werkzeug, which is not installed.
moto-ext 4.2.11.post1 requires werkzeug, which is not installed.
localstack-core 2.2.0 has requirement dill==0.3.2, but you have dill 0.3.7.
localstack-core 2.2.0 has requirement cachetools~=5.0.0, but you have cachetools 3.1.1.
jsonschema-spec 0.1.6 has requirement typing-extensions<4.6.0; python_version < "3.8", but you have typing-extensions 4.7.1.
Flask 2.2.5 requires Werkzeug, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	504/1000 Why? Has a fix available, CVSS 5.8	Insufficient Resource Pool SNYK-PYTHON-CBOR2-6242783	cbor2: 5.4.6 -> 5.6.0	No	No Known Exploit
	819/1000 Why? Currently trending on Twitter, Mature exploit, Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-HYPERCORN-6371005	hypercorn: 0.15.0 -> 0.16.0	No	Mature
	876/1000 Why? Mature exploit, Has a fix available, CVSS 9.8	Improper Access Control SNYK-PYTHON-PYYAML-550022	pyyaml: 5.1 -> 5.4	No	Mature
	704/1000 Why? Has a fix available, CVSS 9.8	Arbitrary Code Execution SNYK-PYTHON-PYYAML-559098	pyyaml: 5.1 -> 5.4	No	No Known Exploit
	876/1000 Why? Mature exploit, Has a fix available, CVSS 9.8	Arbitrary Code Execution SNYK-PYTHON-PYYAML-590151	pyyaml: 5.1 -> 5.4	No	Mature
	539/1000 Why? Has a fix available, CVSS 6.5	Inefficient Algorithmic Complexity SNYK-PYTHON-WERKZEUG-6035177	werkzeug: 2.2.3 -> 2.3.8	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:

🦉 Denial of Service (DoS)
🦉 Improper Access Control
🦉 Arbitrary Code Execution
🦉 More lessons are available in Snyk Learn