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

[Security] Bump django from 2.1.11 to 3.0 #10

Closed
wants to merge 1 commit into from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps django from 2.1.11 to 3.0.

Commits
  • d36413a [3.0.x] Bumped version for 3.0 release.
  • f3da083 [3.0.x] Finalized release notes for Django 3.0.
  • d13ba55 [3.0.x] Added CVE-2019-19118 to the security archive.
  • 4afa0e5 [3.0.x] Updated contrib translations from Transifex
  • 71ec953 [3.0.x] Updated core translations from Transifex
  • 5fca551 [3.0.x] Removed issue reporter name from 2.1.15 and 2.2.8 release notes.
  • 46491e8 [3.0.x] Added release dates for 2.1.15, 2.2.8 and 3.0.
  • 092cd66 Fixed CVE-2019-19118 -- Required edit permissions on parent model for editabl...
  • db0cc4a [3.0.x] Refs #30953 -- Added 2.1.15 release note for 0107e3d1058f653f66032f7f...
  • f4ed680 [3.0.x] Fixed #30953 -- Made select_for_update() lock queryset's model when u...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [django](https://github.com/django/django) from 2.1.11 to 3.0.
- [Release notes](https://github.com/django/django/releases)
- [Commits](django/django@2.1.11...3.0)

Signed-off-by: dependabot-preview[bot] <[email protected]>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Dec 3, 2019
@dependabot-preview
Copy link
Contributor Author

We've just been alerted that this update fixes a security vulnerability:

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects django
Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing. A Django model admin displaying inline related models, where the user has view-only permissions to a parent model but edit permissions to the inline model, would be presented with an editing UI, allowing POST requests, for updating the inline model. Directly editing the view-only parent model was not possible, but the parent model's save() method was called, triggering potential side effects, and causing pre and post-save signal handlers to be invoked. (To resolve this, the Django admin is adjusted to require edit permissions on the parent model in order for inline models to be editable.)

Affected versions: [">= 2.1.0, < 2.1.15"]

@dependabot-preview dependabot-preview bot changed the title Bump django from 2.1.11 to 3.0 [Security] Bump django from 2.1.11 to 3.0 Dec 10, 2019
@dependabot-preview dependabot-preview bot added the security Pull requests that address a security vulnerability label Dec 10, 2019
@dependabot-preview
Copy link
Contributor Author

Superseded by #14.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/django-3.0 branch December 19, 2019 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file security Pull requests that address a security vulnerability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants