metawarc
metawarc copied to clipboard
datacoon
[Snyk] Fix for 8 vulnerabilities
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-dev.txt
Vulnerabilities that will be fixed
By pinning:
| Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity |
|---|---|---|---|---|---|
 |
554/1000 Why? Has a fix available, CVSS 6.8 |
Insufficient Verification of Data Authenticity SNYK-PYTHON-CERTIFI-3164749 |
certifi: 2021.10.8 -> 2023.7.22 |
No | No Known Exploit |
 |
704/1000 Why? Has a fix available, CVSS 9.8 |
Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047 |
certifi: 2021.10.8 -> 2023.7.22 |
No | No Known Exploit |
|
596/1000 Why? Recently disclosed, Has a fix available, CVSS 6.2 |
Resource Exhaustion SNYK-PYTHON-IDNA-6597975 |
idna: 2.10 -> 3.7 |
No | No Known Exploit |
 |
696/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.5 |
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-PYGMENTS-1086606 |
pygments: 2.5.2 -> 2.15.0 |
No | Proof of Concept |
|
589/1000 Why? Has a fix available, CVSS 7.5 |
Denial of Service (DoS) SNYK-PYTHON-PYGMENTS-1088505 |
pygments: 2.5.2 -> 2.15.0 |
No | No Known Exploit |
|
479/1000 Why? Has a fix available, CVSS 5.3 |
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-PYGMENTS-5750273 |
pygments: 2.5.2 -> 2.15.0 |
No | No Known Exploit |
|
519/1000 Why? Has a fix available, CVSS 6.1 |
Information Exposure SNYK-PYTHON-REQUESTS-5595532 |
requests: 2.27.1 -> 2.31.0 |
No | No Known Exploit |
|
509/1000 Why? Has a fix available, CVSS 5.9 |
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412 |
setuptools: 40.5.0 -> 65.5.1 |
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
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
