[Snyk] Security upgrade werkzeug from 2.2.3 to 3.0.3

[juhisingh-qait]

User description

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

moto-ext 4.2.11.post1 requires werkzeug, which is not installed.
localstack-core 2.2.0 has requirement cachetools~=5.0.0, but you have cachetools 5.3.3.
localstack-core 2.2.0 has requirement dill==0.3.2, but you have dill 0.3.7.
Flask 1.0.2 requires Werkzeug, which is not installed.
elasticsearch 6.2.0 has requirement urllib3<1.23,>=1.21.1, but you have urllib3 1.26.18.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	139/1000 Why? Confidentiality impact: High, Integrity impact: High, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): Required, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 9.79, Likelihood: 1.42, Score Version: V5	Remote Code Execution (RCE) SNYK-PYTHON-WERKZEUG-6808933	werkzeug: 2.2.3 -> 3.0.3	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

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.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Remote Code Execution (RCE)

---

PR Type

enhancement

---

Description

• Upgraded werkzeug in requirements.txt to version 3.0.3 to mitigate a known security vulnerability identified by Snyk.
• The upgrade is not directly required by the project but is pinned to avoid potential security issues.

---

Changes walkthrough 📝

	Relevant files
Enhancement	requirements.txt Upgrade werkzeug to Fix Security Vulnerability                      requirements.txt Upgraded werkzeug to version 3.0.3 to address a security vulnerability. +1/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR Description updated to latest commit (607c2b4)

• Copy walkthrough table to "Files Changed" Tab

[codiumai-pr-agent-pro]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the PR involves a simple version upgrade in the requirements.txt file to address a security vulnerability. The change is straightforward and limited to one line, making it easy to review.
🧪 Relevant tests	No
⚡ Possible issues	Dependency Conflicts: The PR warning section indicates potential conflicts with other packages (moto-ext, localstack-core, Flask, elasticsearch) due to the version upgrade of werkzeug. These conflicts might cause runtime issues if not resolved.
🔒 Security concerns	No

[codiumai-pr-agent-pro]

PR Code Suggestions ✨

Category

Suggestions

Best practice

Pin werkzeug to an exact version to ensure consistency and security across different environments. Consider specifying an exact version for werkzeug instead of a version range. This helps ensure that all environments run the same version, which can prevent unexpected behavior due to differences in versions. Using an exact version also aligns with the practice of pinning dependencies to avoid potential future vulnerabilities that could arise in newer versions. requirements.txt [33] -werkzeug>=3.0.3 # not directly required, pinned by Snyk to avoid a vulnerability +werkzeug==3.0.3 # pinned to an exact version to avoid potential inconsistencies and vulnerabilities