[Snyk] Security upgrade fastapi from 0.103.2 to 0.109.1

[AdamOswald]

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

transformers 4.30.2 has requirement tokenizers!=0.11.3,<0.14,>=0.11.1, but you have tokenizers 0.15.1.
torch 1.13.1 requires nvidia-cublas-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-runtime-cu11, which is not installed.
torch 1.13.1 requires nvidia-cudnn-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-nvrtc-cu11, which is not installed.
tensorflow-hub 0.16.1 requires tf-keras, which is not installed.
tensorboard 2.11.2 has requirement protobuf<4,>=3.9.2, but you have protobuf 4.24.4.
tensorboard 2.11.2 has requirement setuptools>=41.0.0, but you have setuptools 39.0.1.
scikit-learn 1.0.2 requires scipy, which is not installed.
python-igraph 0.11.3 has requirement igraph==0.11.3, but you have igraph 0.10.8.
powerlaw 1.5 requires scipy, which is not installed.
pipenv 2023.10.3 has requirement setuptools>=67, but you have setuptools 39.0.1.
paddlenlp 2.7.2 requires fastapi, which is not installed.
paddlenlp 2.7.2 requires seqeval, which is not installed.
paddlenlp 2.7.2 has requirement multiprocess<=0.70.12.2, but you have multiprocess 0.70.15.
paddlenlp 2.7.2 has requirement dill<0.3.5, but you have dill 0.3.7.
paddle2onnx 0.9.5 has requirement onnx<=1.9.0, but you have onnx 1.14.1.
onnxruntime 1.14.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3.
onnxruntime-gpu 1.14.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3.
lpips 0.1.4 requires scipy, which is not installed.
gradio 3.34.0 requires fastapi, which is not installed.
filterpy 1.4.5 requires scipy, which is not installed.
facexlib 0.3.0 requires scipy, which is not installed.
datasets 2.13.2 has requirement dill<0.3.7,>=0.3.0, but you have dill 0.3.7.
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
	768/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-FASTAPI-6228055	fastapi: 0.103.2 -> 0.109.1	No	Proof of Concept

(*) 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:

🦉 Regular Expression Denial of Service (ReDoS)

Summary by CodeRabbit

• Chores
  • Updated FastAPI to version 0.109.1 to address a security vulnerability.

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[secure-code-warrior-for-github]

Micro-Learning Topic: Regular expression denial of service (Detected by phrase)

Matched on "Regular Expression Denial of Service"

What is this? (2min video)

Denial of Service (DoS) attacks caused by Regular Expression which causes the system to hang or cause them to work very slowly when attacker sends a well-crafted input(exponentially related to input size).Denial of service attacks significantly degrade the service quality experienced by legitimate users. These attacks introduce large response delays, excessive losses, and service interruptions, resulting in direct impact on availability.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Denial of service (Detected by phrase)

Matched on "Denial of Service"

The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others. Source: https://www.owasp.org/index.php/Denial_of_Service

Try a challenge in Secure Code Warrior

[difflens]

View changes in DiffLens

[pull-request-quantifier-deprecated]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 1

Change summary by file extension:
.txt : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[senior-dev-bot]

Hi there! 👋 Thanks for opening a PR. 🎉 To get the most out of Senior Dev, please sign up in our Web App, connect your GitHub account, and add/join your organization AdamOswald. After that, you will receive code reviews beginning on your next opened PR. 🚀

[sourcery-ai]

PR Type: Enhancement

PR Summary: This pull request addresses a critical security vulnerability in the FastAPI package by upgrading it from version 0.103.2 to 0.109.1. The upgrade mitigates the risk associated with a Regular Expression Denial of Service (ReDoS) vulnerability, enhancing the security posture of the project. It is part of an automated process initiated by Snyk to maintain the health and security of the project dependencies.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.

• Sourcery currently only approves 'Typo fix' PRs.

✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.

No details provided.

📝 Complexity: the changes are too large or complex for Sourcery to approve.

• Unsupported files: the diff contains files that Sourcery does not currently support during reviews.

General suggestions:

• Ensure that the upgrade does not introduce compatibility issues with other dependencies, especially given the warnings about other package requirements.
• Consider reviewing and updating other dependencies that have known vulnerabilities or compatibility issues as indicated in the PR warnings to further improve project security and stability.
• After merging this PR, it would be beneficial to perform thorough testing of the application to verify that the FastAPI upgrade does not negatively impact any functionalities.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

• X
• Mastodon
• LinkedIn
• Facebook

---

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

[coderabbitai]

Walkthrough

This update focuses on enhancing the security of the application by addressing a specific vulnerability. By adding fastapi>=0.109.1 to the requirements.txt, the change ensures that the application relies on a version of FastAPI that includes necessary patches or improvements, safeguarding against potential security threats.

Changes

File	Change Summary
requirements.txt	Added fastapi>=0.109.1 to address vulnerability

🐇✨
In the garden of code, where vulnerabilities hide,
A patch was planted, with security in stride.
FastAPI grows stronger, with each version anew,
A safer tomorrow, our code hops towards, true.
🌱🔐✨

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 0518dd3 and 23e76c7.

Files selected for processing (1)

• requirements.txt (1 hunks)

Additional comments: 1

requirements.txt (1)

• 113-113: The addition of fastapi>=0.109.1 correctly specifies the minimum required version to address the identified vulnerability. The comment provides clear context for this change.

[difflens]

View changes in DiffLens

[guide-bot]

Thanks for opening this Pull Request!
We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.