Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

[Snyk] Security upgrade django from 2.2.24 to 2.2.27 #416

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

Conversation

snyk-bot
Copy link
Contributor

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/base.txt
⚠️ Warning
requests 2.24.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5.
botocore 1.19.5 has requirement urllib3<1.26,>=1.25.4; python_version != "3.4", but you have urllib3 1.26.5.
awesome-slugify 1.6.5 has requirement Unidecode<0.05,>=0.04.14, but you have Unidecode 1.1.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Access Restriction Bypass
SNYK-PYTHON-DJANGO-2312875
django:
2.2.24 -> 2.2.27
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Directory Traversal
SNYK-PYTHON-DJANGO-2329158
django:
2.2.24 -> 2.2.27
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Information Exposure
SNYK-PYTHON-DJANGO-2329159
django:
2.2.24 -> 2.2.27
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2329160
django:
2.2.24 -> 2.2.27
No No Known Exploit
medium severity 496/1000
Why? Recently disclosed, Has a fix available, CVSS 4.2
Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-2389002
django:
2.2.24 -> 2.2.27
No No Known Exploit
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2389021
django:
2.2.24 -> 2.2.27
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 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

@snyk-bot snyk-bot requested a review from a team as a code owner February 21, 2022 21:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant