Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade sphinx from 1.3.1 to 3.3.0 #49

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kroman0
Copy link
Contributor

@kroman0 kroman0 commented Aug 1, 2023

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
python-coveralls 2.5.0 requires sh, which is not installed.
python-coveralls 2.5.0 requires coverage, which is not installed.
pyramid 2.0.1 requires venusian, which is not installed.
pyramid 2.0.1 requires webob, which is not installed.
pyramid 2.0.1 requires zope.interface, which is not installed.
pyramid 2.0.1 requires zope.deprecation, which is not installed.
plaster-pastedeploy 1.0.1 has requirement PasteDeploy>=2.0, but you have PasteDeploy 1.5.2.
Jinja2 2.7.3 requires markupsafe, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SPHINX-5811865
sphinx:
1.3.1 -> 3.3.0
No Proof of Concept
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SPHINX-5812109
sphinx:
1.3.1 -> 3.3.0
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)

@guardrails
Copy link

guardrails bot commented Aug 1, 2023

⚠️ We detected 3 security issues in this pull request:

Vulnerable Libraries (3)
Severity Details
High pkg:pypi/[email protected] (t) upgrade to: 2.10.1
Critical pkg:pypi/[email protected] (t) upgrade to: 2.1,2.1
N/A pkg:pypi/[email protected] (t) upgrade to: 5.1

More info on how to fix Vulnerable Libraries in Python.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

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