[Snyk] Fix for 17 vulnerabilities

[esquivelgor]

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

qiskit-optimization 0.5.0 requires scipy, which is not installed.
qiskit-optimization 0.5.0 requires qiskit-terra, which is not installed.
qiskit-ibmq-provider 0.20.2 requires qiskit-terra, which is not installed.
qiskit-ibmq-provider 0.20.2 requires websocket-client, which is not installed.
qiskit-aer 0.12.2 requires qiskit-terra, which is not installed.
qiskit-aer 0.12.2 requires scipy, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	539/1000 Why? Has a fix available, CVSS 6.5	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5914629	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Missing Cryptographic Step SNYK-PYTHON-CRYPTOGRAPHY-6036192	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-6050294	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	616/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.9	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6092044	cryptography: 41.0.3 -> 42.0.4	No	Proof of Concept
	696/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.5	Observable Timing Discrepancy SNYK-PYTHON-CRYPTOGRAPHY-6126975	cryptography: 41.0.3 -> 42.0.4	No	Proof of Concept
	509/1000 Why? Has a fix available, CVSS 5.9	Use of a Broken or Risky Cryptographic Algorithm SNYK-PYTHON-CRYPTOGRAPHY-6149518	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Resource Exhaustion SNYK-PYTHON-CRYPTOGRAPHY-6157248	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	489/1000 Why? Has a fix available, CVSS 5.5	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6210214	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6261585	cryptography: 41.0.3 -> 42.0.4	No	No Known Exploit
	531/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 4.2	Remote Code Execution (RCE) SNYK-PYTHON-IPYTHON-3318382	ipython: 7.34.0 -> 8.10.0	No	Proof of Concept
	484/1000 Why? Has a fix available, CVSS 5.4	Cross-site Scripting (XSS) SNYK-PYTHON-JINJA2-6150717	jinja2: 3.1.2 -> 3.1.3	No	No Known Exploit
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	NULL Pointer Dereference SNYK-PYTHON-NUMPY-2321964	numpy: 1.21.3 -> 1.22.2	No	Proof of Concept
	399/1000 Why? Has a fix available, CVSS 3.7	Buffer Overflow SNYK-PYTHON-NUMPY-2321966	numpy: 1.21.3 -> 1.22.2	No	No Known Exploit
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Denial of Service (DoS) SNYK-PYTHON-NUMPY-2321970	numpy: 1.21.3 -> 1.22.2	No	Proof of Concept
	509/1000 Why? Has a fix available, CVSS 5.9	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412	setuptools: 40.5.0 -> 65.5.1	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.26.16 -> 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.26.16 -> 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:

🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Resource Exhaustion
🦉 NULL Pointer Dereference
🦉 More lessons are available in Snyk Learn