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:
test/requirements.txt
⚠️ Warning
```
Jinja2 2.11.3 requires MarkupSafe, which is not installed.
hca 6.3.0 requires cryptography, which is not installed.
google-auth-oauthlib 1.0.0 has requirement google-auth>=2.15.0, but you have google-auth 1.35.0.
boto3 1.26.67 has requirement s3transfer<0.7.0,>=0.6.0, but you have s3transfer 0.2.1.
awscli 1.27.67 has requirement s3transfer<0.7.0,>=0.6.0, but you have s3transfer 0.2.1.
awscli 1.27.67 has requirement docutils<0.17,>=0.10, but you have docutils 0.19.
```
(*) 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.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
⚠️ Warning
``` Jinja2 2.11.3 requires MarkupSafe, which is not installed. hca 6.3.0 requires cryptography, which is not installed. google-auth-oauthlib 1.0.0 has requirement google-auth>=2.15.0, but you have google-auth 1.35.0. boto3 1.26.67 has requirement s3transfer<0.7.0,>=0.6.0, but you have s3transfer 0.2.1. awscli 1.27.67 has requirement s3transfer<0.7.0,>=0.6.0, but you have s3transfer 0.2.1. awscli 1.27.67 has requirement docutils<0.17,>=0.10, but you have docutils 0.19. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 5.9
SNYK-PYTHON-CRYPTOGRAPHY-3172287
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 4.8
SNYK-PYTHON-CRYPTOGRAPHY-3314966
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 5.9
SNYK-PYTHON-CRYPTOGRAPHY-3315324
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 7.4
SNYK-PYTHON-CRYPTOGRAPHY-3315328
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 5.3
SNYK-PYTHON-CRYPTOGRAPHY-3315331
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 5.9
SNYK-PYTHON-CRYPTOGRAPHY-3315452
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 5.9
SNYK-PYTHON-CRYPTOGRAPHY-3315972
cryptography:
2.3.1 -> 39.0.1
Why? Recently disclosed, Has a fix available, CVSS 5.9
SNYK-PYTHON-CRYPTOGRAPHY-3315975
cryptography:
2.3.1 -> 39.0.1
(*) 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) 🦉 Denial of Service (DoS)