Skip to content

[Snyk] Fix for 4 vulnerabilities#8

Open
snyk-bot wants to merge 1 commit intomasterfrom
snyk-fix-003c30be879859d86e886ccd09fa8c05
Open

[Snyk] Fix for 4 vulnerabilities#8
snyk-bot wants to merge 1 commit intomasterfrom
snyk-fix-003c30be879859d86e886ccd09fa8c05

Conversation

@snyk-bot
Copy link
Copy Markdown

@snyk-bot snyk-bot commented Mar 6, 2022

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:
    • test-requirements.txt
⚠️ Warning
Sphinx 1.8.6 requires Pygments, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYGMENTS-1086606
pygments:
2.5.2 -> 2.7.4
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PYGMENTS-1088505
pygments:
2.5.2 -> 2.7.4
No No Known Exploit
medium severity 646/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.5
Cross-site Scripting (XSS)
SNYK-PYTHON-SPHINX-570772
sphinx:
1.8.6 -> 3.0.4
No Proof of Concept
medium severity 636/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Cross-site Scripting (XSS)
SNYK-PYTHON-SPHINX-570773
sphinx:
1.8.6 -> 3.0.4
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 effected 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:

🦉 Cross-site Scripting (XSS)
🦉 Cross-site Scripting (XSS)

@atomist atomist bot added auto-branch-delete:on-close Delete branch when pull request gets closed auto-merge-method:merge Auto-merge with merge commit auto-merge:on-bpr-success Auto-merge on passed branch protection rule labels Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-branch-delete:on-close Delete branch when pull request gets closed auto-merge:on-bpr-success Auto-merge on passed branch protection rule auto-merge-method:merge Auto-merge with merge commit

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant