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

fix: upgrade 5 vulnerable packages #26

Closed

Conversation

satishrudderstack
Copy link

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 Upgrade Breaking Change Exploit Maturity
critical severity 704/1000
Why? Has a fix available, CVSS 9.8
Improper Following of a Certificate's Chain of Trust
SNYK-PYTHON-CERTIFI-5805047
certifi:
2022.12.7 -> 2023.7.22
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYGMENTS-5750273
pygments:
2.11.2 -> 2.15.0
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Information Exposure
SNYK-PYTHON-REQUESTS-5595532
requests:
2.27.1 -> 2.31.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-5926907
urllib3:
1.26.8 -> 1.26.18
No No Known Exploit
medium severity 424/1000
Why? Has a fix available, CVSS 4.2
Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-6002459
urllib3:
1.26.8 -> 1.26.18
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

sonarcloud bot commented Dec 6, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@bardisg bardisg changed the title [Snyk] Fix for 5 vulnerabilities fix: upgrade 5 vulnerable packages Dec 27, 2023
@saikumarrs
Copy link
Member

With the latest release v2.1.1, this PR is not needed anymore.

@saikumarrs saikumarrs closed this Jun 28, 2024
@github-actions github-actions bot deleted the snyk-fix-4892ee3e9b317f2ec1291b40f90a18d1 branch June 29, 2024 00:13
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.

3 participants