[Snyk] Security upgrade cryptography from 41.0.6 to 42.0.2

[thiagoalessio]

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

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	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.6 -> 42.0.2	No	No Known Exploit
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-PYTHON-CRYPTOGRAPHY-6157248	cryptography: 41.0.6 -> 42.0.2	No	No Known Exploit
	451/1000 Why? Recently disclosed, Has a fix available, CVSS 3.3	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6210214	cryptography: 41.0.6 -> 42.0.2	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
🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')
🦉 NULL Pointer Dereference

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from thiagoalessio. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment