[Snyk] Security upgrade requests from 2.31.0 to 2.32.0 by TheRedHatter · Pull Request #2 · TheRedHatter/hackazon · GitHub
Skip to content

[Snyk] Security upgrade requests from 2.31.0 to 2.32.0#2

Open
TheRedHatter wants to merge 1 commit into
masterfrom
snyk-fix-b0ffca1aa663036e0980a201d5d53921
Open

[Snyk] Security upgrade requests from 2.31.0 to 2.32.0#2
TheRedHatter wants to merge 1 commit into
masterfrom
snyk-fix-b0ffca1aa663036e0980a201d5d53921

Conversation

@TheRedHatter

Copy link
Copy Markdown
Owner

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:
    • vendor/guzzlehttp/guzzle/docs/requirements.txt
⚠️ Warning
sphinx 5.3.0 requires requests, which is not installed.

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.

…bilities

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-REQUESTS-6928867

@prisma-cloud-devsecops prisma-cloud-devsecops Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prisma Cloud has found errors in this PR ⬇️

@@ -1,2 +1,3 @@
Sphinx>=1.2b1
guzzle_sphinx_theme>=0.6.0
requests>=2.32.0 # not directly required, pinned by Snyk to avoid a vulnerability

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docutils 0.21.2 / requirements.txt

MEDIUM  Ensure open source packages have OSI-approved licenses (GPL-1.0)

Ensure open source packages have OSI-approved licenses

@@ -1,2 +1,3 @@
Sphinx>=1.2b1
guzzle_sphinx_theme>=0.6.0
requests>=2.32.0 # not directly required, pinned by Snyk to avoid a vulnerability

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

guzzle-sphinx-theme 0.7.11 / requirements.txt

LOW  Ensure package licenses are known or SPDX recognized (UNKNOWN)

Ensure package licenses are known or SPDX recognized

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@TheRedHatter

Copy link
Copy Markdown
Owner Author

Logo
Checkmarx One – Scan Summary & Details04b8fe52-3900-4f6f-be3e-4761ff25c49c

New Issues

Severity Issue Source File / Package Checkmarx Insight
MEDIUM CVE-2023-33202 Maven-org.bouncycastle:bcprov-jdk15on-1.50 Vulnerable Package
MEDIUM CVE-2024-28859 Php-swiftmailer/swiftmailer-v4.3.1 Vulnerable Package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants