Skip to content

Comments

[Snyk] Fix for 2 vulnerabilities#51

Open
jpalomar wants to merge 1 commit intodevelopfrom
snyk-fix-ed60d92863c32dd272a34321feaaad63
Open

[Snyk] Fix for 2 vulnerabilities#51
jpalomar wants to merge 1 commit intodevelopfrom
snyk-fix-ed60d92863c32dd272a34321feaaad63

Conversation

@jpalomar
Copy link

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

  • requirements/base.txt
⚠️ Warning
equests 2.20.1 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 2.0.7.
docker 6.1.3 has requirement requests>=2.26.0, but you have requests 2.20.1.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@jpalomar
Copy link
Author

Merge Risk: High

This is a major version upgrade for both Flask and its core dependency, Werkzeug, introducing significant breaking changes that require developer action.

Flask: 1.0.4 → 3.1.3 (High Risk)

This upgrade spans two major versions (v1 → v3) and includes several breaking changes.

Key Changes:

  • Python Version Support: Support for Python 2.7, 3.5, 3.6, 3.7, and 3.8 has been dropped across the version range.
  • Removed Deprecations: Code deprecated in previous versions has been removed. This includes Config.from_json (replaced by Config.from_file), helpers.total_seconds, and internal context stacks like _app_ctx_stack.
  • Dependency Updates: Requires newer major versions of its dependencies, most notably Werkzeug 3.0.0, which has its own set of breaking changes.
  • Configuration: The FLASK_ENV environment variable is deprecated.

Werkzeug: 2.2.3 → 3.1.6 (High Risk)

The upgrade to Werkzeug 3.x is a primary driver of the breaking changes in Flask 3.x.

Key Changes:

  • Removed Deprecations: Previously deprecated code has been removed.
  • API and Behavior Changes:
    • The data structures for Authorization and WWWAuthenticate headers have been refactored and are no longer dictionaries.
    • The test client's response object is no longer a tuple and its data must be accessed via properties.
    • generate_password_hash now defaults to using scrypt.

Recommendation: This upgrade requires significant testing and code modification. Developers must ensure their environment uses a supported Python version (3.9+). Code should be audited for usage of removed functions and updated to use the new APIs, particularly for configuration loading, header parsing, and interactions with the test client. Given the number of breaking changes, this upgrade should be handled as a dedicated refactoring effort.

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