[Snyk] Security upgrade urllib3 from 1.26.20 to 2.5.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:

🦉 Open Redirect

[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, automatically generated by Snyk, focuses on enhancing the project's security posture by upgrading a critical dependency. It addresses known vulnerabilities in urllib3 by updating it to a more secure version and explicitly pinning this version in the test requirements.

Highlights

• Security Upgrade: The primary change is an automated security upgrade of the urllib3 dependency from version 1.26.20 to 2.5.0 to address two identified vulnerabilities.
• Dependency Pinning: A direct dependency pin for urllib3 has been added to test_requirements/requirements_312_core.txt, explicitly setting it to version 2.5.0.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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, automatically generated by Snyk, aims to fix a security vulnerability in urllib3 by upgrading it to version 2.5.0.

However, this upgrade introduces a critical dependency conflict. The version of requests used in test_requirements/requirements_312_core.txt (2.25.1) is not compatible with urllib3 2.x. This will cause pip install to fail.

I've left a comment detailing the issue and a suggested resolution, which involves upgrading the requests package itself. Please note that other requirements files in this repository also pin requests to versions incompatible with urllib3 2.x and may need similar updates.

[gemini-code-assist]

This change introduces a dependency conflict that will break the installation process.

The requests package version 2.25.1 (pinned on line 1) has a dependency on urllib3<1.27. This conflicts with the newly added requirement urllib3>=2.5.0.

urllib3 version 2.x introduced breaking changes and is not compatible with requests version 2.x.

To resolve this, you should upgrade requests to a version that supports a non-vulnerable version of urllib3. For example, requests>=2.32.0 vendors urllib3 v2.x, which would resolve both the vulnerability and the conflict.

A possible fix would be to update requests on line 1 to requests>=2.32.0 and remove this line, as urllib3 would then be managed as a vendored dependency of requests.