Skip to content

[Snyk] Security upgrade pyjwt from 2.9.0 to 2.13.0#32

Open
mandibles232 wants to merge 1 commit into
mainfrom
snyk-fix-4ebe2eee542061833c2a818aec8a999e
Open

[Snyk] Security upgrade pyjwt from 2.9.0 to 2.13.0#32
mandibles232 wants to merge 1 commit into
mainfrom
snyk-fix-4ebe2eee542061833c2a818aec8a999e

Conversation

@mandibles232

Copy link
Copy Markdown

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):

  • tools/python/requirements.txt

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


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:

🦉 Improper Authentication
🦉 Allocation of Resources Without Limits or Throttling

@mandibles232

Copy link
Copy Markdown
Author

Merge Risk: Medium

This upgrade contains minor breaking changes and significant security enhancements. The risk is assessed as medium due to a dropped Python version support and stricter key validation.

Key Changes:

  • Python Version Support: Support for Python 3.7 (which reached its end-of-life in June 2023) was dropped starting in pyjwt version 2.9.0. [2]
  • Stricter HMAC Key Validation: As of v2.13.0, empty HMAC keys are explicitly rejected with an InvalidKeyError. Previously, this might have only produced a warning. Implementations using empty keys will now fail. [2]
  • Security Fixes: The versions in this range include several important security fixes, including preventing algorithm confusion attacks and addressing issues with issuer claim validation. [2]

Recommendation:

  • Verify that your application is running on Python 3.8 or newer.
  • Confirm that your application is not using empty keys for HMAC algorithms.
  • Review the changelog for the full list of security enhancements and bug fixes.

Source: PyJWT Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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