[Snyk] Fix for 11 vulnerabilities

[robertatakenaka]

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

Flask 1.1.4 has requirement click<8.0,>=5.1, but you have click 8.1.7.
Flask 1.1.4 has requirement itsdangerous<2.0,>=0.24, but you have itsdangerous 2.1.2.
Flask-Limiter 3.5.0 has requirement Flask>=2, but you have Flask 1.1.4.
Flask-JWT-Extended 4.6.0 has requirement Flask<4.0,>=2.0, but you have Flask 1.1.4.
Flask-AppBuilder 4.4.1 has requirement Flask<3.0.0,>=2, but you have Flask 1.1.4.
cattrs 1.10.0 has requirement attrs>=20, but you have attrs 19.3.0.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
argcomplete 1.12.3 has requirement importlib-metadata<5,>=0.23; python_version == "3.7", but you have importlib-metadata 6.7.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	554/1000 Why? Has a fix available, CVSS 6.8	Insufficient Verification of Data Authenticity SNYK-PYTHON-CERTIFI-3164749	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	704/1000 Why? Has a fix available, CVSS 9.8	Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	544/1000 Why? Has a fix available, CVSS 6.6	Insecure Permissions SNYK-PYTHON-FLASKAPPBUILDER-1910931	flask-appbuilder: 1.13.1 -> 2.2.3	No	No Known Exploit
	489/1000 Why? Has a fix available, CVSS 5.5	Incorrect Default Permissions SNYK-PYTHON-FLASKAPPBUILDER-565889	flask-appbuilder: 1.13.1 -> 2.2.3	No	No Known Exploit
	524/1000 Why? Has a fix available, CVSS 6.2	Resource Exhaustion SNYK-PYTHON-IDNA-6597975	idna: 2.10 -> 3.7	No	No Known Exploit
	586/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-MAKO-3017600	mako: 1.1.6 -> 1.2.2	No	Proof of Concept
	696/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-PYGMENTS-1086606	pygments: 2.5.2 -> 2.15.0	No	Proof of Concept
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-PYGMENTS-1088505	pygments: 2.5.2 -> 2.15.0	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-PYGMENTS-5750273	pygments: 2.5.2 -> 2.15.0	No	No Known Exploit
	691/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.4	Use of a Broken or Risky Cryptographic Algorithm SNYK-PYTHON-PYJWT-2840625	pyjwt: 1.7.1 -> 2.4.0	No	Proof of Concept
	519/1000 Why? Has a fix available, CVSS 6.1	Information Exposure SNYK-PYTHON-REQUESTS-5595532	requests: 2.27.1 -> 2.31.0	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:

🦉 Incorrect Default Permissions
🦉 Resource Exhaustion
🦉 Use of a Broken or Risky Cryptographic Algorithm