[Snyk] Security upgrade django from 3.1.3 to 4.2.17

[officialmofabs]

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• dev-projects/my-documaker/code/backend/requirements.txt

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• 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.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Command Injection
🦉 SQL Injection

Summary by Sourcery

Bug Fixes:

• Upgrade Django from version 3.1.3 to 4.2.17 to address security vulnerabilities.

[sourcery-ai]

Reviewer's Guide by Sourcery

This is a security-focused update that upgrades Django from version 3.1.3 to 4.2.17 to address two vulnerabilities identified by Snyk. The implementation is straightforward, involving a direct version bump in the requirements.txt file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Upgrade Django package version to address security vulnerabilities	Update Django version from 3.1.3 to 4.2.17 Address two security vulnerabilities (SNYK-PYTHON-DJANGO-8456315 and SNYK-PYTHON-DJANGO-8456316) Maintain compatibility with existing dependencies (asgiref, psycopg2, pytz, and sqlparse)	dev-projects/my-documaker/code/backend/requirements.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/shell-quote@1.7.2	CVE: GHSA-g4rg-993r-mgx7 Improper Neutralization of Special Elements used in a Command in Shell-quote (CRITICAL) Affected versions: <= 1.7.2 Patched version: 1.7.3	dev-projects/my-documaker/code/frontend/yarn.lock	⚠︎
Possible typosquat attack	npm/xmldom@0.1.31	Did you mean: @xmldom/xmldom	dev-projects/my-documaker/code/frontend/yarn.lock	⚠︎
Critical CVE	npm/xmldom@0.1.31	CVE: GHSA-crh6-fp67-6883 xmldom allows multiple root nodes in a DOM (CRITICAL) Affected versions: <= 0.6.0 Patched version: No patched versions	dev-projects/my-documaker/code/frontend/yarn.lock	⚠︎
Critical CVE	npm/url-parse@1.4.7	CVE: GHSA-hgjh-723h-mx2j Authorization Bypass Through User-Controlled Key in url-parse (CRITICAL) Affected versions: < 1.5.8 Patched version: 1.5.8	dev-projects/my-documaker/code/frontend/yarn.lock	⚠︎
Critical CVE	npm/plist@3.0.1	CVE: GHSA-4cpg-3vgw-4877 Prototype pollution in Plist before 3.0.5 can cause denial of service (CRITICAL) Affected versions: < 3.0.5 Patched version: 3.0.5	dev-projects/my-documaker/code/frontend/yarn.lock	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/shell-quote@1.7.2
• @SocketSecurity ignore npm/xmldom@0.1.31
• @SocketSecurity ignore npm/url-parse@1.4.7
• @SocketSecurity ignore npm/plist@3.0.1