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
```
pandas 0.24.2 requires numpy, which is not installed.
Flask 1.1.1 requires itsdangerous, which is not installed.
Flask 1.1.1 requires Jinja2, which is not installed.
flask-restplus 0.13.0 requires jsonschema, which is not installed.
```
Vulnerabilities that will be fixed
By pinning:
Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity
506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
(*) 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
``` pandas 0.24.2 requires numpy, which is not installed. Flask 1.1.1 requires itsdangerous, which is not installed. Flask 1.1.1 requires Jinja2, which is not installed. flask-restplus 0.13.0 requires jsonschema, which is not installed. ```Vulnerabilities that will be fixed
By pinning:
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321964
numpy:1.21.3 -> 1.22.2Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321966
numpy:1.21.3 -> 1.22.2Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321970
numpy:1.21.3 -> 1.22.2(*) 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:
🦉 NULL Pointer Dereference 🦉 Denial of Service (DoS)