[Snyk] Fix for 2 vulnerabilities

[naiba4]

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements_prod.txt

⚠️ Warning

Flask-Caching 2.1.0 has requirement cachelib<0.10.0,>=0.9.0, but you have cachelib 0.10.2.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• 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.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[changeset-bot]

⚠️ No Changeset found

Latest commit: bd263d0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	werkzeug@​3.1.4
	sqlparse@​0.5.4

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		System shell access: pypi sqlparse Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Network access: pypi werkzeug Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Dynamic code execution: pypi werkzeug Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		System shell access: pypi werkzeug Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: pypi sqlparse URLs: https://www.python.org/dev/peps/pep-0338/, https://docs.python.org/2/using/cmdline.html#cmdoption-m, https://docs.python.org/3/using/cmdline.html#cmdoption-m, http://click.pocoo.org/5/setuptools/#setuptools-integration Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: pypi sqlparse Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: pypi werkzeug Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Potential code anomaly (AI signal): pypi werkzeug is 100.0% likely to have a medium risk anomaly Notes: This code implements an in-process interactive HTML console intended for debugging. There is no clear evidence of malware or obfuscation in the fragment. The main security concern is that it executes arbitrary Python code provided to Console.eval (exec), and it modifies global interpreter state (sys.displayhook, sys.stdout) — both are legitimate for a debugger but dangerous if the console is exposed to untrusted input or used in production contexts. Treat exposure of Console.eval to external/untrusted users as high risk; the module itself appears non-malicious. Confidence: 1.00 Severity: 0.60 From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: pypi werkzeug Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: pypi werkzeug URLs: https://httpwg.org/specs/rfc9110.html#abnf.extension, https://httpwg.org/specs/rfc9110.html#field.accept, http://browsercookielimits.squawky.net/, http://xn--n3h.net/p%C3%A5th?q=%C3%A8ry%DF, https://example.com/app/ Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: pypi werkzeug URLs: https://github.com/pallets/werkzeug/issues/%s, https://github.com/pallets/werkzeug/pull/%s, https://github.com/advisories/GHSA-%s, https://docs.python.org/3/, https://palletsprojects.com/donate, https://pypi.org/project/Werkzeug/, https://github.com/pallets/werkzeug/, https://github.com/pallets/werkzeug/issues/, https://discord.gg/pallets, https://lucumr.pocoo.org/, https://lucumr.pocoo.org/feed.atom, https://pyside.blogspot.com/, https://pyside.blogspot.com/feeds/posts/default, https://blog.ianbicking.org/, https://blog.ianbicking.org/feed/, http://amix.dk/, https://feeds.feedburner.com/amixdk, https://www.cmlenz.net/blog/, https://www.cmlenz.net/blog/atom.xml, https://effbot.org/, https://effbot.org/rss.xml, https://httpwg.org/specs/rfc9110.html#abnf.extension, https://httpwg.org/specs/rfc9110.html#field.accept, http://browsercookielimits.squawky.net/, http://xn--n3h.net/p%C3%A5th?q=%C3%A8ry%DF, https://example.com/app/, https://github.com/pallets/werkzeug/issues/1344, https://github.com/python/cpython/pull/3249, http://example.org/, http://example.org/test/bar/, http://example.org/bar/, http://example.org/bar/?aha=muhaha, http://example.org/bar/?foo=bar, http://example.com/, http://example.org/abc/, http://example.org/foo, http://example.org/bar/blub, http://example.org/bar/50, http://example.org/bar/0.815, http://example.org/bar/la/di, http://example.org/test/, http://example.org/test/foo, http://example.org/test/bar/blub, http://example.org/test/bar/50, http://example.org/test/bar/0.815, http://example.org/test/bar/la/di, https://example.org/foo, http://wiki.example.com/, http://test.localhost/foo, https://github.com/pallets/werkzeug/issues/709, https://github.com/pallets/werkzeug/issues/2590, http://example.org/x:y, http://example.org:5000/, http://example.com, http://www.example.com/foo/, http://my.domain.com/, http://www.domain.com/, http://www.google.com/, http://example.com/foo%20bar, http://xn--n3h.example.com/%D0%B2%D0%BE%D0%B9%D1%82%D0%B8/, http://xn--n3h.example.com/foo+bar/, http://example.com/approot/, http://example.org/foo/bar, http://gamma.example.com/, http://missing.test:1337/index.html#ignore, https://github.com/pallets/werkzeug/pull/838, https://tools.ietf.org/html/rfc3875#section-4.1.18, https://tools.ietf.org/html/rfc2616#section-2.2, https://tools.ietf.org/html/rfc2616#section-3.6.1, http://test.example.com/login, http://example.com/bar, http://example.com/bar/, https://foo.invalid/test/, https://example.com/base, http://xn--n3h.net/, http://example.com/foo, http://www.example.com/?x=23, http://test.com/%3Fmeh?foo=%26%2F, http://test.com/%3Fmeh?foo=%26/, http://xn--f-1gaa.com:8080/bam/baz, http://xn--f-1gaa.com/%2F%25?q=%C3%B6&x=%3D%25#%25, http://www.idempoten.ce, http://xn--f-rgao.com/%C3%9E, http://xn--f-rgao.com/%E2%98%90/fred?utf8=%E2%9C%93, https://test.example/path, http://xn--n3h.example.com/, http://example.com/?xss=, http://example.com/redirect, http://example.org/app, http://example.org/app/foo/, http://example.org/foo/bar/, http://example.org/app/foo/bar/, http://example.org/foo/?baz, http://example.org/foo/, http://example.org/app/, http://example.com/test, http://example.com/test/bar?foo=baz, http://example.com/test/bar, http://example.com/test/, https://example.com/test, http://www.example.com/?next%3D/baz%23my%3Dhash, http://example.com/bar?next=, https://palletsprojects.com, http://www.example.com/ Location: Package overview From: requirements_prod.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report