[Snyk] Fix for 8 vulnerabilities

[rhanka]

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

scikit-learn 1.0.2 requires scipy, which is not installed.
rejson 0.5.6 has requirement redis==3.5.3, but you have redis 5.0.4.
redisearch 2.1.1 has requirement redis==3.5.3, but you have redis 5.0.4.
Flask 2.2.5 requires Werkzeug, which is not installed.
Flask-Login 0.6.3 requires Werkzeug, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	NULL Pointer Dereference SNYK-PYTHON-NUMPY-2321964	numpy: 1.21.3 -> 1.22.2	No	Proof of Concept
	399/1000 Why? Has a fix available, CVSS 3.7	Buffer Overflow SNYK-PYTHON-NUMPY-2321966	numpy: 1.21.3 -> 1.22.2	No	No Known Exploit
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Denial of Service (DoS) SNYK-PYTHON-NUMPY-2321970	numpy: 1.21.3 -> 1.22.2	No	Proof of Concept
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Exposure of Data Element to Wrong Session SNYK-PYTHON-REDIS-5291195	redis: 3.5.3 -> 4.3.6	No	Proof of Concept
	344/1000 Why? Has a fix available, CVSS 2.6	Access Restriction Bypass SNYK-PYTHON-WERKZEUG-3319935	werkzeug: 0.16.1 -> 3.0.3	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-WERKZEUG-3319936	werkzeug: 0.16.1 -> 3.0.3	No	No Known Exploit
	539/1000 Why? Has a fix available, CVSS 6.5	Inefficient Algorithmic Complexity SNYK-PYTHON-WERKZEUG-6035177	werkzeug: 0.16.1 -> 3.0.3	No	No Known Exploit
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Remote Code Execution (RCE) SNYK-PYTHON-WERKZEUG-6808933	werkzeug: 0.16.1 -> 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:

🦉 NULL Pointer Dereference
🦉 Access Restriction Bypass
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn

[coderabbitai]

Important

Auto Review Skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.