[Snyk] Security upgrade jinja2 from 2.11.3 to 3.1.3

[billmetangmo]

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

Werkzeug 2.2.3 has requirement MarkupSafe>=2.1.1, but you have MarkupSafe 1.1.1.
Jinja2 3.1.3 has requirement MarkupSafe>=2.0, but you have MarkupSafe 1.1.1.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	556/1000 Why? Recently disclosed, Has a fix available, CVSS 5.4	Cross-site Scripting (XSS) SNYK-PYTHON-JINJA2-6150717	jinja2: 2.11.3 -> 3.1.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:

🦉 Cross-site Scripting (XSS)

[github-actions]

Infracost report

💰 Monthly cost will not change

_{This comment will be updated when code changes.}

[billmetangmo]

❌ Plan Failed

CI link

Error: "name" cannot be longer than 64 characters: "mtchoun-mouh-snyk-fix-6326d0e314f4279f83eafbb2472e6060-trigger_user_scan"
 
   with aws_cloudwatch_event_rule.scheduler,
   on main.tf line 288, in resource "aws_cloudwatch_event_rule" "scheduler":
  288:   name                = (terraform.workspace == "mtchoun-mouh-master") ? "trigger_user_scan" : "${terraform.workspace}-trigger_user_scan"
 

Operation failed: failed running terraform plan (exit 1)