Skip to content

[Snyk] Fix for 2 vulnerabilities#716

Open
alejandrosuarez wants to merge 1 commit into
mainfrom
snyk-fix-dcca5bdedfae0beafab3bd94bccac336
Open

[Snyk] Fix for 2 vulnerabilities#716
alejandrosuarez wants to merge 1 commit into
mainfrom
snyk-fix-dcca5bdedfae0beafab3bd94bccac336

Conversation

@alejandrosuarez
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • examples/research_projects/onnxruntime/textual_inversion/requirements.txt
⚠️ Warning
transformers 4.30.2 requires safetensors, which is not installed.
torchvision 0.14.1 requires torch, which is not installed.
tensorboard 2.11.2 requires protobuf, which is not installed.
accelerate 0.20.3 requires torch, which is not installed.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • 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.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

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

…ments.txt to reduce vulnerabilities

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-PROTOBUF-15090738
- https://snyk.io/vuln/SNYK-PYTHON-TORCH-15123585
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @alejandrosuarez, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to enhance the security posture of the project by automatically updating specific Python package versions to mitigate known vulnerabilities. It focuses on resolving issues related to protobuf and torch within a research project's dependency list, ensuring that the project utilizes more secure versions of these critical libraries.

Highlights

  • Automated Vulnerability Fixes: This pull request was automatically generated by Snyk to address two identified security vulnerabilities within the project's pip dependencies.
  • Dependency Version Updates: The requirements.txt file for the textual_inversion example has been updated to pin protobuf to version 6.33.5 and torch to version 2.10.0 to mitigate known vulnerabilities.
Changelog
  • examples/research_projects/onnxruntime/textual_inversion/requirements.txt
    • Pinned protobuf to version 6.33.5 to resolve a vulnerability (SNYK-PYTHON-PROTOBUF-15090738).
    • Pinned torch to version 2.10.0 to resolve a vulnerability (SNYK-PYTHON-TORCH-15123585).
Activity
  • The pull request was automatically generated by Snyk.
  • The PR description includes a warning about potential missing dependencies (safetensors, torch, protobuf) that are required by other packages but not directly installed.
  • It explicitly states that some vulnerabilities might not be fully fixed due to complex dependency graphs.
  • Provides links to Snyk reports, documentation, and interactive lessons for further information.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request from Snyk aims to fix two security vulnerabilities by updating protobuf and torch. However, the proposed versions for both packages are invalid. protobuf>=6.33.5 specifies a non-existent version and would also conflict with tensorboard's requirements. torch>=2.10.0 is also a non-existent version, likely a typo for 2.1.0. These issues will break dependency installation and are marked as critical. Please review the suggested versions and correct them.

ftfy
tensorboard
modelcards
protobuf>=6.33.5 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The specified version 6.33.5 for protobuf does not appear to exist on PyPI, which will cause dependency installation to fail. Additionally, tensorboard (a dependency in this project) requires protobuf<4. Pinning to a version >=4 would create a dependency conflict. Please specify a valid version of protobuf that is <4 and fixes the vulnerability.

tensorboard
modelcards
protobuf>=6.33.5 # not directly required, pinned by Snyk to avoid a vulnerability
torch>=2.10.0 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The specified version 2.10.0 for torch appears to be a typo and does not exist on PyPI. This will cause the dependency installation to fail. It's likely the intended version was 2.1.0.

torch>=2.1.0 # not directly required, pinned by Snyk to avoid a vulnerability

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: PyTorch: pypi torch`.load` with `weights_only=True` leads to remote code execution

CVE: GHSA-53q9-r3pm-6pq6 PyTorch: torch.load with weights_only=True leads to remote code execution (CRITICAL)

Affected versions: < 2.6.0

Patched version: 2.6.0

From: examples/research_projects/realfill/requirements.txtpypi/torch@2.2.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/torch@2.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Critical
Critical CVE: PyTorch: pypi torch`.load` with `weights_only=True` leads to remote code execution

CVE: GHSA-53q9-r3pm-6pq6 PyTorch: torch.load with weights_only=True leads to remote code execution (CRITICAL)

Affected versions: < 2.6.0

Patched version: 2.6.0

From: examples/server/requirements.txtpypi/torch@2.4.1

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/torch@2.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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