collaborative-open-plant-omics / COPO

Collaborative Open Plant Omics
MIT License
17 stars 4 forks source link

[Snyk] Fix for 30 vulnerabilities #172

Closed snyk-bot closed 1 year ago

snyk-bot commented 2 years ago

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 ``` mzml2isa 0.5.1 requires openpyxl, which is not installed. jupyter 1.0.0 requires jupyter-console, which is not installed. isatools 0.9.5 requires numpy, which is not installed. isatools 0.9.5 requires networkx, which is not installed. isatools 0.9.5 requires pandas, which is not installed. ipython 5.10.0 requires simplegeneric, which is not installed. ipython 5.10.0 has requirement prompt-toolkit<2.0.0,>=1.0.4, but you have prompt-toolkit 2.0.10. django-tools 0.39.0 requires Django, which is not installed. django-redis-sessions 0.5.6 requires redis, which is not installed. django-gollum 1.0.1 requires django, which is not installed. django-appconf 1.0.3 requires django, which is not installed. django-allow-cidr 0.3.1 requires Django, which is not installed. django-allauth 0.46.0 requires Django, which is not installed. biopython 1.73 requires numpy, which is not installed. ```

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
low severity 369/1000
Why? Has a fix available, CVSS 3.1
Directory Traversal
SNYK-PYTHON-DJANGO-1066259
django:
3.1 -> 3.2.15
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Web Cache Poisoning
SNYK-PYTHON-DJANGO-1076802
django:
3.1 -> 3.2.15
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Directory Traversal
SNYK-PYTHON-DJANGO-1090612
django:
3.1 -> 3.2.15
No No Known Exploit
low severity 379/1000
Why? Has a fix available, CVSS 3.3
Directory Traversal
SNYK-PYTHON-DJANGO-1279042
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
HTTP Header Injection
SNYK-PYTHON-DJANGO-1290072
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Directory Traversal
SNYK-PYTHON-DJANGO-1298665
django:
3.1 -> 3.2.15
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Improper Input Validation
SNYK-PYTHON-DJANGO-1298666
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
SQL Injection
SNYK-PYTHON-DJANGO-1315688
django:
3.1 -> 3.2.15
No Proof of Concept
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Access Restriction Bypass
SNYK-PYTHON-DJANGO-2312875
django:
3.1 -> 3.2.15
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Directory Traversal
SNYK-PYTHON-DJANGO-2329158
django:
3.1 -> 3.2.15
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Information Exposure
SNYK-PYTHON-DJANGO-2329159
django:
3.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2329160
django:
3.1 -> 3.2.15
No No Known Exploit
medium severity 424/1000
Why? Has a fix available, CVSS 4.2
Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-2389002
django:
3.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2389021
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 624/1000
Why? Has a fix available, CVSS 8.2
SQL Injection
SNYK-PYTHON-DJANGO-2606966
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 731/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
SQL Injection
SNYK-PYTHON-DJANGO-2606969
django:
3.1 -> 3.2.15
No Proof of Concept
critical severity 776/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.1
SQL Injection
SNYK-PYTHON-DJANGO-2940618
django:
3.1 -> 3.2.15
No Proof of Concept
high severity 564/1000
Why? Has a fix available, CVSS 7
Reflected File Download (RFD)
SNYK-PYTHON-DJANGO-2968205
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Insecure Permissions
SNYK-PYTHON-DJANGO-609368
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 634/1000
Why? Has a fix available, CVSS 8.4
Insecure Permissions
SNYK-PYTHON-DJANGO-609369
django:
3.1 -> 3.2.15
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-1047473
lxml:
4.1.1 -> 4.9.1
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Arbitrary File Write
SNYK-PYTHON-LXML-1047474
lxml:
4.1.1 -> 4.9.1
No No Known Exploit
medium severity 529/1000
Why? Has a fix available, CVSS 6.3
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-1088006
lxml:
4.1.1 -> 4.9.1
No No Known Exploit
high severity 624/1000
Why? Has a fix available, CVSS 8.2
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-2316995
lxml:
4.1.1 -> 4.9.1
No No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
NULL Pointer Dereference
SNYK-PYTHON-LXML-2940874
lxml:
4.1.1 -> 4.9.1
No Proof of Concept
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-72651
lxml:
4.1.1 -> 4.9.1
No No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
NULL Pointer Dereference
SNYK-PYTHON-NUMPY-2321964
numpy:
1.20.0 -> 1.22.2
No Proof of Concept
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Buffer Overflow
SNYK-PYTHON-NUMPY-2321966
numpy:
1.20.0 -> 1.22.2
No No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Buffer Overflow
SNYK-PYTHON-NUMPY-2321969
numpy:
1.20.0 -> 1.22.2
No Proof of Concept
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Denial of Service (DoS)
SNYK-PYTHON-NUMPY-2321970
numpy:
1.20.0 -> 1.22.2
No Proof of Concept

(*) 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:

🦉 Directory Traversal 🦉 Directory Traversal 🦉 Directory Traversal 🦉 More lessons are available in Snyk Learn