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 #11928

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Aug 1, 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:
    • requirements.txt
⚠️ Warning
ultralytics 8.0.145 requires scipy, which is not installed.
torch 1.13.1 requires nvidia-cublas-cu11, which is not installed.
torch 1.13.1 requires nvidia-cudnn-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-nvrtc-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-runtime-cu11, which is not installed.

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)

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Upgrade to minimum required NumPy version for YOLOv5.

📊 Key Changes

  • Updated the minimum required version of NumPy from 1.18.5 to 1.22.2.

🎯 Purpose & Impact

  • Purpose: Ensure compatibility with newer features or performance improvements in NumPy that YOLOv5 may rely on.
  • Impact: Users may need to update their NumPy installation, which could lead to better performance and access to the latest NumPy functionalities. However, it could also potentially introduce conflicts with other dependencies if they require an older NumPy version. 🔄

@glenn-jocher glenn-jocher merged commit 3f76b80 into master Aug 1, 2023
9 checks passed
@glenn-jocher glenn-jocher deleted the snyk-fix-d21d60931ed2d4e453525c64ee9ee9b2 branch August 1, 2023 12:40
pleb631 pushed a commit to pleb631/yolov5 that referenced this pull request Jan 6, 2024
fix: requirements.txt to reduce vulnerabilities


The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-NUMPY-2321964
- https://snyk.io/vuln/SNYK-PYTHON-NUMPY-2321966
- https://snyk.io/vuln/SNYK-PYTHON-NUMPY-2321970

Co-authored-by: snyk-bot <snyk-bot@snyk.io>
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.

None yet

2 participants