[Snyk] Fix for 30 vulnerabilities

[dealako]

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:
  • scripts/audits/requirements.txt

⚠️ Warning

moto 1.3.14 has requirement idna<2.9,>=2.5, but you have idna 3.7.
botocore 1.13.50 has requirement urllib3<1.26,>=1.20; python_version >= "3.4", but you have urllib3 2.0.7.
aws-sam-translator 1.82.0 has requirement boto3==1.*,>=1.19.5, but you have boto3 1.10.7.

Vulnerabilities that will be fixed

By pinning:

Severity	Issue	Upgrade	Breaking Change	Exploit Maturity
	Insufficient Verification of Data Authenticity SNYK-PYTHON-CERTIFI-3164749	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3172287	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Expected Behavior Violation SNYK-PYTHON-CRYPTOGRAPHY-3314966	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Use After Free SNYK-PYTHON-CRYPTOGRAPHY-3315324	cryptography: 3.3.2 -> 42.0.2	No	Proof of Concept
	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-PYTHON-CRYPTOGRAPHY-3315328	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Timing Attack SNYK-PYTHON-CRYPTOGRAPHY-3315331	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315452	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315972	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315975	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3316038	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3316211	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5663682	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Improper Certificate Validation SNYK-PYTHON-CRYPTOGRAPHY-5777683	cryptography: 3.3.2 -> 42.0.2	No	Proof of Concept
	Insufficient Verification of Data Authenticity SNYK-PYTHON-CRYPTOGRAPHY-5813745	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813746	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813750	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5914629	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Missing Cryptographic Step SNYK-PYTHON-CRYPTOGRAPHY-6036192	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-6050294	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6092044	cryptography: 3.3.2 -> 42.0.2	No	Proof of Concept
	Observable Timing Discrepancy SNYK-PYTHON-CRYPTOGRAPHY-6126975	cryptography: 3.3.2 -> 42.0.2	No	Proof of Concept
	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6210214	cryptography: 3.3.2 -> 42.0.2	No	No Known Exploit
	Resource Exhaustion SNYK-PYTHON-IDNA-6597975	idna: 2.10 -> 3.7	No	No Known Exploit
	Cross-site Scripting (XSS) SNYK-PYTHON-JINJA2-6150717	jinja2: 2.11.3 -> 3.1.3	No	No Known Exploit
	Deserialization of Untrusted Data SNYK-PYTHON-NETWORKX-1062709	networkx: 2.2 -> 2.6	No	No Known Exploit
	Information Exposure SNYK-PYTHON-REQUESTS-5595532	requests: 2.27.1 -> 2.31.0	No	No Known Exploit
	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412	setuptools: 40.5.0 -> 65.5.1	No	No Known Exploit
	Access Restriction Bypass SNYK-PYTHON-WERKZEUG-3319935	werkzeug: 1.0.1 -> 2.2.3	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-WERKZEUG-3319936	werkzeug: 1.0.1 -> 2.2.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 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:

🦉 Use After Free
🦉 Access of Resource Using Incompatible Type ('Type Confusion')
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn