[Snyk] Security upgrade pyasn1 from 0.4.8 to 0.6.2

[doublegate]

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

Snyk changed the following file(s):

• api/requirements.txt

⚠️ Warning

shapely 2.0.2 requires numpy, which is not installed.
python-jose 3.4.0 has requirement pyasn1<0.5.0,>=0.4.1, but you have pyasn1 0.5.1.
email-validator 2.1.0 requires dnspython, 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 @doublegate, 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 automates a critical security update for the pyasn1 library, aiming to resolve a known vulnerability. The change ensures that the project's dependencies are secure by upgrading pyasn1 to a patched version, thereby enhancing the overall security posture without introducing new features or functional changes.

Highlights

• Security Upgrade: This pull request, automatically generated by Snyk, upgrades the pyasn1 dependency from version 0.4.8 to 0.6.2 to address a security vulnerability.
• Vulnerability Fix: The upgrade specifically targets and fixes one identified vulnerability within the project's pip dependencies, enhancing the project's security posture.
• Dependency Management: The change is confined to api/requirements.txt, where pyasn1 is now explicitly pinned to version 0.6.2 as a direct requirement to mitigate the security risk.

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, automatically generated by Snyk, aims to upgrade pyasn1 to version 0.6.2 to address a security vulnerability. However, this upgrade introduces a critical dependency conflict with the python-jose package, which will cause the application's dependency installation to fail. The python-jose package requires a version of pyasn1 that is incompatible with the proposed secure version, and there is no newer version of python-jose available that resolves this conflict. Therefore, this pull request cannot be merged in its current state as it would break the build.

[gemini-code-assist]

This upgrade of pyasn1 to version >=0.6.2 creates a critical dependency conflict that will break the application build.

The python-jose==3.4.0 package, specified on line 44, requires pyasn1<0.5.0. This new requirement for pyasn1>=0.6.2 is mutually exclusive with the existing dependency, which will cause pip install to fail with a dependency resolution error.

The security vulnerability in pyasn1 requires an upgrade to version 0.5.0 or newer. Since the latest version of python-jose (3.4.0) does not support this, a direct upgrade of pyasn1 is not possible while keeping python-jose.

This PR cannot be merged as it will break the dependency installation. A different approach is needed, such as finding an alternative to python-jose or waiting for an updated version that supports a secure pyasn1.

[Copilot]

Pull request overview

Updates the API’s pip dependencies to address a Snyk-reported vulnerability by explicitly pinning a safer pyasn1 version.

Changes:

• Add pyasn1>=0.6.2 to api/requirements.txt as a Snyk vulnerability pin.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.