Weaver: Workflow Execution Management Service (EMS); Application, Deployment and Execution Service (ADES); OGC API - Processes; WPS; CWL Application Package
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
```
schema-salad 8.4.20230808163024 has requirement ruamel.yaml<0.18,>=0.16.12, but you have ruamel.yaml 0.18.5.
rdflib 6.3.2 has requirement importlib-metadata<5.0.0,>=4.0.0; python_version >= "3.7" and python_version < "3.8", but you have importlib-metadata 6.7.0.
pywps 4.5.2 requires werkzeug, which is not installed.
json2xml 4.0.1 has requirement urllib3==1.26.13, but you have urllib3 2.0.7.
geotiff 0.2.10 requires pyproj, which is not installed.
cwltool 3.1.20230906142556 has requirement ruamel.yaml<0.18,>=0.15, but you have ruamel.yaml 0.18.5.
cwl-utils 0.28 has requirement ruamel.yaml<0.18,>=0.16.12, but you have ruamel.yaml 0.18.5.
cwl-utils 0.28 has requirement ruamel.yaml<0.18,>=0.17.6; python_version >= "3.7", but you have ruamel.yaml 0.18.5.
cwl-upgrader 1.2.8 has requirement ruamel.yaml<0.18,>=0.15.71, but you have ruamel.yaml 0.18.5.
celery 5.3.0 has requirement kombu<6.0,>=5.3.0, but you have kombu 5.3.0b3.
botocore 1.31.77 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
```
#### Vulnerabilities that will be fixed
##### By pinning:
Severity | Issue | Upgrade | Breaking Change | Exploit Maturity
:-------------------------:|:-------------------------|:-------------------------|:-------------------------|:-------------------------
 | Denial of Service (DoS) [SNYK-PYTHON-WERKZEUG-6041510](https://snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6041510) | `werkzeug:` `2.2.3 -> 3.0.1` | No | No Known Exploit
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](https://app.snyk.io/org/fmigneault/project/e70ab783-8025-473e-9f7c-3b18a705d514?utm_source=github&utm_medium=referral&page=fix-pr)
🛠 [Adjust project settings](https://app.snyk.io/org/fmigneault/project/e70ab783-8025-473e-9f7c-3b18a705d514?utm_source=github&utm_medium=referral&page=fix-pr/settings)
📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities)
[//]: # (snyk:metadata:{"prId":"c15dbee3-0832-4dcb-ad60-b7fbea13248d","prPublicId":"c15dbee3-0832-4dcb-ad60-b7fbea13248d","dependencies":[{"name":"werkzeug","from":"2.2.3","to":"3.0.1"}],"packageManager":"pip","projectPublicId":"e70ab783-8025-473e-9f7c-3b18a705d514","projectUrl":"https://app.snyk.io/org/fmigneault/project/e70ab783-8025-473e-9f7c-3b18a705d514?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-WERKZEUG-6041510"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown"],"priorityScoreList":[null],"remediationStrategy":"vuln"})
---
**Learn how to fix vulnerabilities with free interactive lessons:**
🦉 [Denial of Service (DoS)](https://learn.snyk.io/lesson/redos/?loc=fix-pr)
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
``` schema-salad 8.4.20230808163024 has requirement ruamel.yaml<0.18,>=0.16.12, but you have ruamel.yaml 0.18.5. rdflib 6.3.2 has requirement importlib-metadata<5.0.0,>=4.0.0; python_version >= "3.7" and python_version < "3.8", but you have importlib-metadata 6.7.0. pywps 4.5.2 requires werkzeug, which is not installed. json2xml 4.0.1 has requirement urllib3==1.26.13, but you have urllib3 2.0.7. geotiff 0.2.10 requires pyproj, which is not installed. cwltool 3.1.20230906142556 has requirement ruamel.yaml<0.18,>=0.15, but you have ruamel.yaml 0.18.5. cwl-utils 0.28 has requirement ruamel.yaml<0.18,>=0.16.12, but you have ruamel.yaml 0.18.5. cwl-utils 0.28 has requirement ruamel.yaml<0.18,>=0.17.6; python_version >= "3.7", but you have ruamel.yaml 0.18.5. cwl-upgrader 1.2.8 has requirement ruamel.yaml<0.18,>=0.15.71, but you have ruamel.yaml 0.18.5. celery 5.3.0 has requirement kombu<6.0,>=5.3.0, but you have kombu 5.3.0b3. botocore 1.31.77 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7. ```[SNYK-PYTHON-WERKZEUG-6041510](https://snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6041510) | `werkzeug:`
`2.2.3 -> 3.0.1`
| No | No Known Exploit 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: