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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 19 vulnerabilities #69

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented May 1, 2023

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:
    • big/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
SQL Injection
SNYK-PYTHON-DJANGO-2606966
django:
1.6.1 -> 3.2.18
No No Known Exploit
critical severity 811/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
SQL Injection
SNYK-PYTHON-DJANGO-2606969
django:
1.6.1 -> 3.2.18
No Proof of Concept
critical severity 776/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.1
SQL Injection
SNYK-PYTHON-DJANGO-2940618
django:
1.6.1 -> 3.2.18
No Proof of Concept
high severity 564/1000
Why? Has a fix available, CVSS 7
Reflected File Download (RFD)
SNYK-PYTHON-DJANGO-2968205
django:
1.6.1 -> 3.2.18
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-3319450
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 494/1000
Why? Has a fix available, CVSS 5.6
Arbitrary Code Execution
SNYK-PYTHON-DJANGO-40025
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Cross-site Request Forgery (CSRF)
SNYK-PYTHON-DJANGO-40026
django:
1.6.1 -> 3.2.18
No No Known Exploit
critical severity 704/1000
Why? Has a fix available, CVSS 9.8
SQL Injection
SNYK-PYTHON-DJANGO-40027
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Web Cache Poisoning
SNYK-PYTHON-DJANGO-40256
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Open Redirect
SNYK-PYTHON-DJANGO-40257
django:
1.6.1 -> 3.2.18
No No Known Exploit
high severity 619/1000
Why? Has a fix available, CVSS 8.1
DNS Rebinding
SNYK-PYTHON-DJANGO-40440
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Open Redirect
SNYK-PYTHON-DJANGO-40460
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Open Redirect
SNYK-PYTHON-DJANGO-40461
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 626/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.1
Open Redirect
SNYK-PYTHON-DJANGO-42178
django:
1.6.1 -> 3.2.18
No Proof of Concept
high severity 701/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.6
SQL Injection
SNYK-PYTHON-DJANGO-559326
django:
1.6.1 -> 3.2.18
No Proof of Concept
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Content Spoofing
SNYK-PYTHON-DJANGO-72888
django:
1.6.1 -> 3.2.18
No No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-JINJA2-1012994
jinja2:
2.7.2 -> 2.11.3
No Proof of Concept
medium severity 554/1000
Why? Has a fix available, CVSS 6.8
Sandbox Escape
SNYK-PYTHON-JINJA2-174126
jinja2:
2.7.2 -> 2.11.3
No No Known Exploit
high severity 644/1000
Why? Has a fix available, CVSS 8.6
Sandbox Bypass
SNYK-PYTHON-JINJA2-455616
jinja2:
2.7.2 -> 2.11.3
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:

馃 SQL Injection
馃 Denial of Service (DoS)
馃 Arbitrary Code Execution
馃 More lessons are available in Snyk Learn

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.

None yet

1 participant