[Snyk] Security upgrade cryptography from 3.3.2 to 41.0.3

[chandrasekarMariappan]

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

openapi-spec-validator 0.5.7 has requirement jsonschema<4.18.0,>=4.0.0, but you have jsonschema 3.1.1.
openapi-schema-validator 0.4.4 has requirement jsonschema<4.18.0,>=4.0.0, but you have jsonschema 3.1.1.
jsonschema-spec 0.1.6 has requirement requests<3.0.0,>=2.31.0, but you have requests 2.26.0.
jsonschema-spec 0.1.6 has requirement typing-extensions<4.6.0; python_version < "3.8", but you have typing-extensions 4.7.1.
jsonschema-spec 0.1.6 has requirement jsonschema<4.18.0,>=4.0.0, but you have jsonschema 3.1.1.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	471/1000 Why? Recently disclosed, Has a fix available, CVSS 3.7	Insufficient Verification of Data Authenticity SNYK-PYTHON-CRYPTOGRAPHY-5813745	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	551/1000 Why? Recently disclosed, Has a fix available, CVSS 5.3	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813746	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	471/1000 Why? Recently disclosed, Has a fix available, CVSS 3.7	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813750	cryptography: 3.3.2 -> 41.0.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:

🦉 Denial of Service (DoS)