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

fix(dependencies): update django to 4.2.13 #449

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

Conversation

kojiromike
Copy link
Contributor

- CVE-2024-24680 (patched in 4.2.10)
- CVE-2024-27351 (patched in 4.2.11)
@kojiromike
Copy link
Contributor Author

Might I suggest enabling dependabot or dependabot security updates, to make this process more automatic? (It isn't something I can simply PR because it isn't my repo.)

@rominf
Copy link

rominf commented Jul 12, 2024

Having pinned versions of requirements prevents dependent packages from updating in case of vulnerabilities. So, now all packages that use Mercury have vulnerable Django installed along with other requirements, and it is not possible to fix this without breaking Mercury's requirements.
image

@kojiromike
Copy link
Contributor Author

Django 4.2.14 is released with additional vulnerabilities that need to be fixed. https://www.djangoproject.com/weblog/2024/jul/09/security-releases/

@kojiromike
Copy link
Contributor Author

Django 4.2.15 fixes three security issues with severity “moderate”, one security issue with severity “high”, and a regression in 4.2.14.

https://docs.djangoproject.com/en/5.0/releases/4.2.15/

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.

2 participants