[Snyk] Fix for 19 vulnerabilities

[somidax]

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/requirements.txt

⚠️ Warning

eth-tester 0.1.0b21 has requirement eth-utils<2.0.0,>=1.0.1, but you have eth-utils 0.7.4.
eth-keys 0.2.0b3 has requirement eth-utils<2.0.0,>=1.0.0-beta.2, but you have eth-utils 0.7.4.
eth-keyfile 0.6.0 has requirement eth-utils<3,>=2, but you have eth-utils 0.7.4.
eth-keyfile 0.6.0 has requirement eth-keys<0.5.0,>=0.4.0, but you have eth-keys 0.2.0b3.
eth-abi 4.2.1 has requirement eth-utils>=2.0.0, but you have eth-utils 0.7.4.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	554/1000 Why? Has a fix available, CVSS 6.8	Insufficient Verification of Data Authenticity SNYK-PYTHON-CERTIFI-3164749	certifi: 2018.1.18 -> 2023.7.22	No	No Known Exploit
	704/1000 Why? Has a fix available, CVSS 9.8	Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047	certifi: 2018.1.18 -> 2023.7.22	No	No Known Exploit
	536/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 4.3	Denial of Service (DoS) SNYK-PYTHON-ETHABI-6085292	eth-abi: 0.5.0 -> 5.0.1	No	Proof of Concept
	586/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.3	Resource Exhaustion SNYK-PYTHON-ETHABI-6394102	eth-abi: 0.5.0 -> 5.0.1	No	Proof of Concept
	399/1000 Why? Has a fix available, CVSS 3.7	Timing Attack SNYK-PYTHON-ETHKEYFILE-2391482	eth-keyfile: 0.5.1 -> 0.6.0	No	No Known Exploit
	524/1000 Why? Has a fix available, CVSS 6.2	Resource Exhaustion SNYK-PYTHON-IDNA-6597975	idna: 2.6 -> 3.7	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-PYCRYPTODOME-42184	pycryptodome: 3.4.11 -> 3.19.1	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Observable Timing Discrepancy SNYK-PYTHON-PYCRYPTODOME-6145007	pycryptodome: 3.4.11 -> 3.19.1	No	No Known Exploit
	549/1000 Why? Has a fix available, CVSS 6.7	Use of a Broken or Risky Cryptographic Algorithm SNYK-PYTHON-PYCRYPTODOME-6219994	pycryptodome: 3.4.11 -> 3.19.1	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Information Exposure SNYK-PYTHON-REQUESTS-5595532	requests: 2.18.4 -> 2.31.0	No	No Known Exploit
	811/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.8	Information Exposure SNYK-PYTHON-REQUESTS-72435	requests: 2.18.4 -> 2.31.0	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.18	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.18	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.18	No	Mature
	589/1000 Why? Has a fix available, CVSS 7.5	Improper Certificate Validation SNYK-PYTHON-URLLIB3-174464	urllib3: 1.22 -> 1.26.18	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Information Exposure Through Sent Data SNYK-PYTHON-URLLIB3-5926907	urllib3: 1.22 -> 1.26.18	No	No Known Exploit
	584/1000 Why? Has a fix available, CVSS 7.4	Information Exposure Through Sent Data SNYK-PYTHON-URLLIB3-5969479	urllib3: 1.22 -> 1.26.18	No	No Known Exploit
	424/1000 Why? Has a fix available, CVSS 4.2	Information Exposure Through Sent Data SNYK-PYTHON-URLLIB3-6002459	urllib3: 1.22 -> 1.26.18	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.18	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)
🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 CRLF injection