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:High] werkzeug Remote Code Execution (RCE) (Due 06/07/2024) #5819

Closed
1 task
cnlucas opened this issue May 8, 2024 · 1 comment
Closed
1 task

[Snyk:High] werkzeug Remote Code Execution (RCE) (Due 06/07/2024) #5819

cnlucas opened this issue May 8, 2024 · 1 comment
Labels
Security: general General security concern or issue Security: high Remediate within 30 days
Milestone

Comments

@cnlucas
Copy link
Member

cnlucas commented May 8, 2024

Introduced through
[email protected]
Fixed in
[email protected]

Exploit maturity
No known exploit

Detailed paths and remediation

Introduced through: [email protected][email protected][email protected]
Fix: Pin werkzeug to version 3.0.3

Introduced through: [email protected][email protected][email protected][email protected]
Fix: Pin werkzeug to version 3.0.3
Introduced through: [email protected][email protected][email protected][email protected][email protected]
Fix: Pin werkzeug to version 3.0.3

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

Snyk: [CVSS 7.5](https://security.snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6808933) - High 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 Remote Code Execution (RCE) due to insufficient hostname checks and the use of relative paths to resolve requests. When the debugger is enabled, an attacker can convince a user to enter their own PIN to interact with a domain and subdomain they control, and thereby cause malicious code to be executed.

The demonstrated attack vector requires a number of conditions that render this attack very difficult to achieve, especially if the victim application is running in the recommended configuration of not having the debugger enabled in production.

Completion Criteria

  • We have either determined this is not a risk and ignored the flag or vuln is remediated
@cnlucas cnlucas added Security: high Remediate within 30 days Security: general General security concern or issue labels May 8, 2024
@cnlucas cnlucas added this to the 25.2 milestone May 8, 2024
@tmpayton
Copy link
Contributor

fixed with this pr #5813

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: high Remediate within 30 days
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants