Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk: Med] werkzeug Inefficient Algorithmic Complexity (Due 12/31/23) #5637

Closed
3 tasks
cnlucas opened this issue Nov 1, 2023 · 2 comments
Closed
3 tasks
Assignees
Labels
Security: general General security concern or issue Security: moderate Remediate within 60 days
Milestone

Comments

@cnlucas
Copy link
Member

cnlucas commented Nov 1, 2023

Introduced through
locust@2.14.2
Fixed in
werkzeug@3.0.1

Exploit maturity
No known exploit

Detailed paths and remediation

Introduced through: project@0.0.0 › locust@2.14.2 › werkzeug@2.2.3
Fix: Pin werkzeug to version 3.0.1

Introduced through: project@0.0.0 › locust@2.14.2 › flask@2.2.5 › werkzeug@2.2.3
Fix: Pin werkzeug to version 3.0.1
Introduced through: project@0.0.0 › locust@2.14.2 › flask-basicauth@0.2.0 › flask@2.2.5 › werkzeug@2.2.3
Fix: Pin werkzeug to version 3.0.1

…and 1 more
Security information
Factors contributing to the scoring:

Snyk: [CVSS 6.5](https://security.snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6035177) - Medium Severity
NVD: Not available. NVD has not yet published its analysis.

Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in multipart data parsing. An attacker can cause a denial of service and block worker processes from handling legitimate requests by sending crafted multipart data to an endpoint that will parse it, eventually exhausting or killing all available workers.

Exploiting this vulnerability is possible if the uploaded file starts with CR or LF and is followed by megabytes of data without these characters.

Action items: (This is lower prioirity buyt can be handled with other werkzeug issue)

  • Verify this is still a vulnerability, or update ticket to reflect this is not an issue and close
  • Address by pinning werkzeug to version 3.0.1

Completion criteria:

  • Vulnerability no longer appearing in snyk
@cnlucas cnlucas added Security: moderate Remediate within 60 days Security: general General security concern or issue labels Nov 1, 2023
@cnlucas cnlucas added this to the Sprint 23.4 milestone Nov 1, 2023
@cnlucas
Copy link
Member Author

cnlucas commented Nov 1, 2023

This is for requirements-dev

@pkfec
Copy link
Contributor

pkfec commented Dec 21, 2023

see ##5636

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Security: general General security concern or issue Security: moderate Remediate within 60 days
Projects
Archived in project
Development

No branches or pull requests

3 participants