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 scrapy from 2.9.0 to 2.11.2 #168

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

Conversation

hackerMrYu
Copy link
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:
    • requirements.txt
⚠️ Warning
twisted 23.8.0 requires zope-interface, which is not installed.
Scrapy 2.9.0 has requirement cryptography>=3.4.6, but you have cryptography 2.8.
pyOpenSSL 24.1.0 has requirement cryptography<43,>=41.0.5, but you have cryptography 2.8.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Exposure of Sensitive Information to an Unauthorized Actor
SNYK-PYTHON-SCRAPY-6841708
scrapy:
2.9.0 -> 2.11.2
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Files or Directories Accessible to External Parties
SNYK-PYTHON-SCRAPY-6841836
scrapy:
2.9.0 -> 2.11.2
No No Known Exploit
medium severity 501/1000
Why? Recently disclosed, Has a fix available, CVSS 4.3
URL Redirection to Untrusted Site ('Open Redirect')
SNYK-PYTHON-SCRAPY-6841882
scrapy:
2.9.0 -> 2.11.2
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:

🦉 URL Redirection to Untrusted Site ('Open Redirect')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants