[Snyk] Security upgrade urllib3 from 1.26.20 to 2.6.0

[nn6n]

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

Snyk changed the following file(s):

• test_requirements/requirements_312_core.txt

⚠️ Warning

equests 2.25.1 requires urllib3, 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:

🦉 Allocation of Resources Without Limits or Throttling

[gemini-code-assist]

Summary of Changes

Hello @nn6n, I'm Gemini Code Assist¹! 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 focuses on enhancing the project's security posture by updating a critical dependency. Automatically generated by Snyk, it specifically targets and resolves two known vulnerabilities associated with the urllib3 package, ensuring the project benefits from the latest security patches without requiring manual intervention for the upgrade process.

Highlights

• Security Upgrade: This pull request upgrades the urllib3 dependency from version 1.26.20 to 2.6.0 to address two identified security vulnerabilities.
• Automated Fix: The changes were automatically generated by Snyk to provide a direct fix for the detected vulnerabilities in the project's pip dependencies.

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. ↩

[gemini-code-assist]

Code Review

This pull request from Snyk aims to upgrade urllib3 to fix security vulnerabilities. However, the proposed change to version 2.6.0 introduces a critical dependency conflict with requests==2.25.1, which requires urllib3<1.27. This will break the installation of test dependencies for Python 3.12. Additionally, this security fix has only been applied to the requirements file for Python 3.12, leaving other environments (for Python 3.8, 3.9, 3.10, and 3.11) potentially vulnerable as they use the same version of requests. The dependency conflict needs to be resolved, and the fix should be applied consistently across all relevant requirement files.

[gemini-code-assist]

This change introduces a dependency conflict. The requests==2.25.1 package specified on line 1 has a requirement for urllib3<1.27. This line adds a conflicting requirement of urllib3>=2.6.0, which will cause dependency resolution to fail.

To resolve this, you could either:

1. Upgrade requests to a version compatible with urllib3 v2.x (e.g., requests>=2.30.0). This would likely need to be done for all requirements*.txt files.
2. Pin urllib3 to a secure version from the 1.x branch that is compatible with requests==2.25.1. For example, urllib3==1.26.18 is the latest in the 1.x series and contains security fixes.