[Snyk] Security upgrade requests from 2.28.2 to 2.32.0 #96

Open
ElBe-Plaq wants to merge 1 commits from snyk-fix-ad7c4a2013aa45376b4f414ea0aacab4 into main
ElBe-Plaq commented 2024-05-22 02:34:58 +00:00 (Migrated from github.com)

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

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 566/1000
Why? Recently disclosed, Has a fix available, CVSS 5.6
Always-Incorrect Control Flow Implementation
SNYK-PYTHON-REQUESTS-6928867
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


Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

<p>This PR was automatically created by Snyk using the credentials of a real user.</p><br /><h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - requirements.txt #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (\*) | Issue | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png 'medium severity') | **566/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 5.6 | Always-Incorrect Control Flow Implementation <br/>[SNYK-PYTHON-REQUESTS-6928867](https://snyk.io/vuln/SNYK-PYTHON-REQUESTS-6928867) | 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: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiIwMjkwNWIzNC1kYWFlLTRkNTEtYWMwNS1lM2E3YzkwYTA5NGUiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6IjAyOTA1YjM0LWRhYWUtNGQ1MS1hYzA1LWUzYTdjOTBhMDk0ZSJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/elbe-plaq/project/db5b4f2d-86b0-4d9d-b22f-175ac2a5fb40?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/elbe-plaq/project/db5b4f2d-86b0-4d9d-b22f-175ac2a5fb40?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # 'snyk:metadata:{"customTemplate":{"variablesUsed":[],"fieldsUsed":[]},"dependencies":[{"name":"requests","from":"2.28.2","to":"2.32.0"}],"env":"prod","issuesToFix":[{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-REQUESTS-6928867","priority_score":566,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"5.6","score":280},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Always-Incorrect Control Flow Implementation"}],"prId":"02905b34-daae-4d51-ac05-e3a7c90a094e","prPublicId":"02905b34-daae-4d51-ac05-e3a7c90a094e","packageManager":"pip","priorityScoreList":[566],"projectPublicId":"db5b4f2d-86b0-4d9d-b22f-175ac2a5fb40","projectUrl":"https://app.snyk.io/org/elbe-plaq/project/db5b4f2d-86b0-4d9d-b22f-175ac2a5fb40?utm_source=github&utm_medium=referral&page=fix-pr","prType":"fix","templateFieldSources":{"branchName":"default","commitMessage":"default","description":"default","title":"default"},"templateVariants":["updated-fix-title","priorityScore"],"type":"auto","upgrade":[],"vulns":["SNYK-PYTHON-REQUESTS-6928867"],"patch":[],"isBreakingChange":false,"remediationStrategy":"vuln"}' --- **Note:** _This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our [documentation.](https://docs.snyk.io/scan-using-snyk/snyk-open-source/automatic-and-manual-prs-with-snyk-open-source/customize-pr-templates-closed-beta)_ **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Learn about vulnerability in an interactive lesson of Snyk Learn.](https://learn.snyk.io/?loc&#x3D;fix-pr)
This pull request has changes conflicting with the target branch.
  • requirements.txt

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin snyk-fix-ad7c4a2013aa45376b4f414ea0aacab4:snyk-fix-ad7c4a2013aa45376b4f414ea0aacab4
git checkout snyk-fix-ad7c4a2013aa45376b4f414ea0aacab4
Sign in to join this conversation.
No description provided.