Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 13 vulnerabilities #85

Closed

Conversation

spolti
Copy link
Owner

@spolti spolti commented Feb 16, 2024

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:
    • docs/samples/explanation/alibi/income/requirements.txt
⚠️ Warning
wasabi 1.1.2 has requirement typing-extensions<4.5.0,>=3.7.4.1; python_version < "3.8", but you have typing-extensions 4.7.1.
thinc 8.2.3 has requirement typing-extensions<4.5.0,>=3.7.4.1; python_version < "3.8", but you have typing-extensions 4.7.1.
spacy 3.7.4 has requirement typing-extensions<4.5.0,>=3.7.4.1; python_version < "3.8", but you have typing-extensions 4.7.1.
scikit-learn 1.0.2 requires scipy, which is not installed.
confection 0.1.4 has requirement typing-extensions<4.5.0,>=3.7.4.1; python_version < "3.8", but you have typing-extensions 4.7.1.
alibi 0.9.3 requires scipy, which is not installed.
alibi 0.9.3 requires transformers, which is not installed.
alibi 0.9.3 requires scikit-image, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 589/1000
Why? Has a fix available, CVSS 7.5
XML External Entity (XXE) Injection
SNYK-PYTHON-FONTTOOLS-6133203
fonttools:
4.38.0 -> 4.43.0
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.21.3 -> 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.21.3 -> 1.22.2
No No Known Exploit
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.21.3 -> 1.22.2
No Proof of Concept
critical severity 909/1000
Why? Mature exploit, Has a fix available, CVSS 9.6
Heap-based Buffer Overflow
SNYK-PYTHON-PILLOW-5918878
pillow:
9.5.0 -> 10.2.0
No Mature
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-PYTHON-PILLOW-6043904
pillow:
9.5.0 -> 10.2.0
No No Known Exploit
high severity 726/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Eval Injection
SNYK-PYTHON-PILLOW-6182918
pillow:
9.5.0 -> 10.2.0
No Proof of Concept
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-6219984
pillow:
9.5.0 -> 10.2.0
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-6219986
pillow:
9.5.0 -> 10.2.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:
39.0.1 -> 65.5.1
No No Known Exploit
high severity 711/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.8
Deserialization of Untrusted Data
SNYK-PYTHON-TRANSFORMERS-6134594
transformers:
4.30.2 -> 4.37.0
No Proof of Concept
critical severity 771/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9
Deserialization of Untrusted Data
SNYK-PYTHON-TRANSFORMERS-6135747
transformers:
4.30.2 -> 4.37.0
No Proof of Concept
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Command Injection
SNYK-PYTHON-TRANSFORMERS-6220003
transformers:
4.30.2 -> 4.37.0
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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 XML External Entity (XXE) Injection
🦉 NULL Pointer Dereference
🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')
🦉 More lessons are available in Snyk Learn

@spolti spolti force-pushed the release-v0.11.1 branch 2 times, most recently from a072a29 to 7d1632b Compare April 11, 2024 19:14
@spolti spolti closed this Jun 26, 2024
@spolti spolti deleted the snyk-fix-ba81d054e23f4cf5f872b078659ff8ae branch June 26, 2024 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants