Opened 7 years ago

Closed 6 years ago

#28517 closed Cleanup/optimization (fixed)

admin does not check if a model has default_permissions before raising PermissionDenied

Reported by: Paulo Owned by: nobody
Component: contrib.admin Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no



Given the following models:

class Product(models.Model):
    name = models.CharField(max_length=200)

    def __str__(self):

class ProductMeta(models.Model):
    name = models.CharField(max_length=200)
    product = models.ForeignKey(to=Product, on_delete=models.CASCADE)

    class Meta:
        default_permissions = ()

    def __str__(self):

class InternalProduct(Product):

    class Meta:
        proxy = True
        default_permissions = ()


  • All models are registered with the admin.
  • Current user is staff with all permissions (non-superuser).

Create Product instances:

  • product_a = Product.objects.create(name='product a')
  • product_b = Product.objects.create(name='product b')

Create ProductMeta instances:

  • ProductMeta.objects.create(name='product a metadata', product=product_a)
  • ProductMeta.objects.create(name='product b metadata', product=product_b)

The following two scenarios will fail:

  • User tries to delete a Product from admin.
  • User tries to delete an InternalProduct from admin.

The first scenario fails because the admin checks if user has delete permission on the collected objects without checking if the delete permission is present on the default_permissions for the collected models.

The second scenario fails because the has_x_permission checks assume add/change/delete are present in default_permissions.

Attachments (1)

28517.patch (650 bytes ) - added by Paulo 7 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by Tim Graham, 7 years ago

Component: Uncategorizedcontrib.admin
Type: UncategorizedCleanup/optimization

The documentation for Options.default_permissions says, "You may customize this list, for example, by setting this to an empty list if your app doesn’t require any of the default permissions." Since the admin app requires those permissions, it seems that setting default_permissions to an empty list would be invalid for this case.

Do you have a use case and proposal for changing the behavior?

by Paulo, 7 years ago

Attachment: 28517.patch added

comment:2 by Paulo, 7 years ago

Because the admin allows us to override the has_x_permission methods, I think the main problem is the delete check buried in get_deleted_objects.
The main use-case I see is to support creating proxy models that need to override parts of the admin for the base model but do not need their own permissions.
This is achievable by setting default_permissions to empty on the proxy model and pointing all has_x_permission methods to the same logic from the base model.
I've attached a patch (untested) which I think fixes this. I can push a PR later today with tests.

comment:3 by Paulo, 7 years ago

Pushed test-case with proposed solution.

comment:4 by Tim Graham, 7 years ago

Has patch: set
Triage Stage: UnreviewedAccepted

comment:5 by Tim Graham <timograham@…>, 6 years ago

Resolution: fixed
Status: newclosed

In d1286a8a:

Fixed #28517 -- Fixed admin delete confirmation view crash when related models don't have a delete permission.

Note: See TracTickets for help on using tickets.
Back to Top