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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Security upgrade django from 1.11.29 to 3.2.20 #48

Closed
wants to merge 4 commits into from
Closed

[Snyk] Security upgrade django from 1.11.29 to 3.2.20 #48

wants to merge 4 commits into from

Conversation

MaggieFero
Copy link
Collaborator

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 
opentelemetry-api 1.16.0 has requirement importlib-metadata>=5.0.0; python_version == "3.7", but you have importlib-metadata 4.13.0.
flower 1.2.0 requires tornado, which is not installed.
celery 5.3.0 requires kombu, which is not installed.
botocore 1.29.165 has requirement urllib3<1.27,>=1.25.4, but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
low severity 25/1000
Why? Confidentiality impact: Low, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): Required, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00148, Social Trends: No, Days since published: 1138, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Low, Package Popularity Score: 96, Impact: 2.35, Likelihood: 1.05, Score Version: V5		 Directory Traversal
SNYK-PYTHON-DJANGO-1066259		 django:
1.11.29 -> 3.2.20
No No Known Exploit
low severity 26/1000
Why? Confidentiality impact: Low, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): Low, Attack Complexity: Low, Attack Vector: Local, EPSS: 0.00214, Social Trends: No, Days since published: 1046, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Low, Package Popularity Score: 96, Impact: 2.35, Likelihood: 1.07, Score Version: V5		 Directory Traversal
SNYK-PYTHON-DJANGO-1279042		 django:
1.11.29 -> 3.2.20
No No Known Exploit
high severity 97/1000
Why? Confidentiality impact: Low, Integrity impact: Low, Availability impact: Low, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00167, Social Trends: No, Days since published: 1044, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 96, Impact: 5.62, Likelihood: 1.71, Score Version: V5		 HTTP Header Injection
SNYK-PYTHON-DJANGO-1290072		 django:
1.11.29 -> 3.2.20
No No Known Exploit
high severity 103/1000
Why? Confidentiality impact: High, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00106, Social Trends: No, Days since published: 1017, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 96, Impact: 5.99, Likelihood: 1.71, Score Version: V5		 Directory Traversal
SNYK-PYTHON-DJANGO-1298665		 django:
1.11.29 -> 3.2.20
No No Known Exploit
medium severity 41/1000
Why? Confidentiality impact: Low, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.0011, Social Trends: No, Days since published: 828, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 96, Impact: 2.35, Likelihood: 1.71, Score Version: V5		 Access Restriction Bypass
SNYK-PYTHON-DJANGO-2312875		 django:
1.11.29 -> 3.2.20
No No Known Exploit
low severity 36/1000
Why? Confidentiality impact: None, Integrity impact: Low, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00134, Social Trends: No, Days since published: 801, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Low, Package Popularity Score: 96, Impact: 2.35, Likelihood: 1.49, Score Version: V5		 Directory Traversal
SNYK-PYTHON-DJANGO-2329158		 django:
1.11.29 -> 3.2.20
No No Known Exploit
low severity 36/1000
Why? Confidentiality impact: Low, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00127, Social Trends: No, Days since published: 801, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Low, Package Popularity Score: 96, Impact: 2.35, Likelihood: 1.49, Score Version: V5		 Information Exposure
SNYK-PYTHON-DJANGO-2329159		 django:
1.11.29 -> 3.2.20
No No Known Exploit
medium severity 41/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: Low, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00221, Social Trends: No, Days since published: 801, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 96, Impact: 2.35, Likelihood: 1.71, Score Version: V5		 Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2329160		 django:
1.11.29 -> 3.2.20
No No Known Exploit
medium severity 52/1000
Why? Confidentiality impact: Low, Integrity impact: Low, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): Required, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00313, Social Trends: No, Days since published: 773, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 4.19, Likelihood: 1.23, Score Version: V5		 Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-2389002		 django:
1.11.29 -> 3.2.20
No No Known Exploit
high severity 115/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00917, Social Trends: No, Days since published: 773, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 1.91, Score Version: V5		 Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2389021		 django:
1.11.29 -> 3.2.20
No No Known Exploit
critical severity 168/1000
Why? Confidentiality impact: High, Integrity impact: High, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00317, Social Trends: No, Days since published: 704, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Critical, Package Popularity Score: 96, Impact: 9.79, Likelihood: 1.72, Score Version: V5		 SQL Injection
SNYK-PYTHON-DJANGO-2606966		 django:
1.11.29 -> 3.2.20
No No Known Exploit
critical severity 242/1000
Why? Confidentiality impact: High, Integrity impact: High, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00296, Social Trends: No, Days since published: 704, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Critical, Package Popularity Score: 96, Impact: 9.79, Likelihood: 2.46, Score Version: V5		 SQL Injection
SNYK-PYTHON-DJANGO-2606969		 django:
1.11.29 -> 3.2.20
No Proof of Concept
critical severity 214/1000
Why? Confidentiality impact: High, Integrity impact: High, Availability impact: None, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00552, Social Trends: No, Days since published: 620, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Critical, Package Popularity Score: 96, Impact: 8.63, Likelihood: 2.47, Score Version: V5		 SQL Injection
SNYK-PYTHON-DJANGO-2940618		 django:
1.11.29 -> 3.2.20
No Proof of Concept
high severity 132/1000
Why? Confidentiality impact: Low, Integrity impact: High, Availability impact: Low, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00361, Social Trends: No, Days since published: 590, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 7.84, Likelihood: 1.68, Score Version: V5		 Reflected File Download (RFD)
SNYK-PYTHON-DJANGO-2968205		 django:
1.11.29 -> 3.2.20
No No Known Exploit
high severity 114/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00172, Social Trends: No, Days since published: 395, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 1.89, Score Version: V5		 Denial of Service (DoS)
SNYK-PYTHON-DJANGO-3319450		 django:
1.11.29 -> 3.2.20
No No Known Exploit
medium severity 49/1000
Why? Confidentiality impact: None, Integrity impact: Low, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00127, Social Trends: No, Days since published: 316, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 2.35, Likelihood: 2.06, Score Version: V5		 Arbitrary File Upload
SNYK-PYTHON-DJANGO-5496950		 django:
1.11.29 -> 3.2.20
No No Known Exploit
high severity 124/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00136, Social Trends: No, Days since published: 256, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.06, Score Version: V5		 Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-DJANGO-5750790		 django:
1.11.29 -> 3.2.20
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:

🦉 Directory Traversal
🦉 Access Restriction Bypass
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn

MaggieFero and others added 4 commits February 27, 2024 13:54
@MaggieFero @phildini
Add privileges to codeql-analysis.yml
aaa31b4 
Explicitly give codeql-analysis action the security-events: write permission so it still works even when the default GitHub Actions token is set to read-only.
@phildini
Bump versions on libraries (#10)
f0567ed 
* Bump versions

* Bump back Pillow due to test failure

* Bump setuptools
@MaggieFero
Merge branch 'bookwyrm-social:main' into main
9e17662
@snyk-bot
fix: requirements.txt to reduce vulnerabilities
970bab2 
The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1066259
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1279042
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1290072
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1298665
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2312875
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2329158
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2329159
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2329160
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2389002
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2389021
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2606966
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2606969
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2940618
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2968205
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-3319450
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-5496950
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-5750790
@MaggieFero
Copy link
Collaborator Author

This is a duplicate of #45 and should be handled there.

@MaggieFero MaggieFero closed this Mar 16, 2024
@MaggieFero MaggieFero deleted the snyk-fix-5b66d329c9a5b5e32444ce311f6d83d2 branch March 16, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@MaggieFero @phildini @snyk-bot