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] Security upgrade ray from 2.0.0 to 2.8.0 #25

Closed
wants to merge 1 commit into from

Conversation

spolti
Copy link
Owner

@spolti spolti commented Nov 19, 2023

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/aif/germancredit/server/requirements.txt
⚠️ Warning
scikit-learn 1.0.2 requires scipy, which is not installed.
kubernetes 28.1.0 has requirement urllib3<2.0,>=1.24.2, but you have urllib3 2.0.7.
kserve 0.10.2 requires ray, which is not installed.
kserve 0.10.2 has requirement avro>=1.11.0, but you have avro file-.avro-VERSION.txt.
kserve 0.10.2 has requirement numpy>=1.21.5, but you have numpy 1.21.3.
botocore 1.32.3 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
aif360 0.5.0 requires scipy, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
critical severity 858/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 9.3
Use of GET Request Method With Sensitive Query Strings
SNYK-PYTHON-RAY-6068111
ray:
2.0.0 -> 2.8.0
No Proof of Concept
critical severity 893/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 10
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
SNYK-PYTHON-RAY-6068115
ray:
2.0.0 -> 2.8.0
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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

…t to reduce vulnerabilities

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-RAY-6068111
- https://snyk.io/vuln/SNYK-PYTHON-RAY-6068115
@spolti spolti changed the base branch from master to cves December 5, 2023 14:44
@spolti spolti changed the base branch from cves to master December 5, 2023 14:44
@spolti spolti closed this Jun 26, 2024
@spolti spolti deleted the snyk-fix-b1d9d54244e1f3f7adf71b10f1d123ca branch June 26, 2024 19:03
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