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 numpy from 1.21.3 to 1.22.2 #23

Closed
wants to merge 1 commit into from

Conversation

spolti
Copy link
Owner

@spolti spolti commented Nov 13, 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/v1beta1/triton/fastertransformer/transformer/requirements.txt
⚠️ Warning
ray 2.0.0 has requirement protobuf<4.0.0,>=3.15.3, but you have protobuf 4.24.4.
ray 2.0.0 has requirement grpcio<=1.43.0,>=1.28.1; python_version < "3.10", but you have grpcio 1.59.2.
kubernetes 28.1.0 has requirement urllib3<2.0,>=1.24.2, but you have urllib3 2.0.7.
kserve 0.10.2 has requirement numpy>=1.21.5, but you have numpy 1.21.3.
botocore 1.31.84 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
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

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

@spolti spolti closed this Jun 26, 2024
@spolti spolti deleted the snyk-fix-f0a10b4f7f7e33bdd74f7a3f0b4ebacc 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