Skip to content

[Snyk] Security upgrade cryptography from 47.0.0 to 48.0.1#23

Open
mandibles232 wants to merge 1 commit into
masterfrom
snyk-fix-21c01344821143a80c225efa2a55882d
Open

[Snyk] Security upgrade cryptography from 47.0.0 to 48.0.1#23
mandibles232 wants to merge 1 commit into
masterfrom
snyk-fix-21c01344821143a80c225efa2a55882d

Conversation

@mandibles232

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements.txt

Breaking Change Risk

Merge Risk: High

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:

🦉 Out-of-bounds Read

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-17344551
@mandibles232

Copy link
Copy Markdown
Author

Merge Risk: High

This major version upgrade introduces several breaking changes, including dropping support for an older Python version and stricter validation rules.

Breaking Changes in 48.0.0:

  • Python 3.8 Support Removed: cryptography now requires Python 3.9 or later. Builds will fail in environments using Python 3.8.
  • Stricter X.509 CRL Validation: Loading an X.509 Certificate Revocation List (CRL) will now raise a ValueError if the inner and outer signature algorithms do not match. Previously, this was only caught during signature validation.
  • Build Process Changes: For users who build the package from source against a custom OpenSSL version, the environment variables for linking (CFLAGS, LDFLAGS, etc.) are no longer supported and a new configuration method is required.

Recommendation: Before upgrading, ensure your environment is running Python 3.9+. Review any code that parses X.509 CRLs to handle potential ValueError exceptions from the stricter validation. If you build from source with a custom OpenSSL, you must update your build scripts.

Source: Cryptography 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