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 pygments from 2.5.2 to 2.7.4 #922

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

Conversation

a-luna
Copy link
Owner

@a-luna a-luna commented Mar 20, 2024

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-dev.txt
⚠️ Warning
virtualenv 20.25.1 has requirement distlib<1,>=0.3.7, but you have distlib 0.3.4.
virtualenv 20.25.1 has requirement filelock<4,>=3.12.2, but you have filelock 3.7.1.
virtualenv 20.25.1 has requirement platformdirs<5,>=3.9.1, but you have platformdirs 2.5.2.
virtualenv 20.25.1 has requirement importlib-metadata>=6.6; python_version < "3.8", but you have importlib-metadata 4.12.0.
ipykernel 6.15.0 requires ipython, which is not installed.
ipdb 0.13.9 requires ipython, which is not installed.
flake8 4.0.1 has requirement importlib-metadata<4.3; python_version < "3.8", but you have importlib-metadata 4.12.0.
black 21.12b0 has requirement tomli<2.0.0,>=0.2.6, but you have tomli 2.0.1.

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

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

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • We don't currently review documentation changes - Let us know if you'd like us to change this.
  • We don't currently review these file types - Let us know if you'd like us to change this.
  • All of the files are larger than we can process. We're working on it!

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