Skip to content

Security issue with default _User class permissions (new apps only) #387

Description

@jamiechapman

I have recently noticed that a new parse-server project (i.e. one that hasn't been migrated from hosted Parse) has a security issue with the _User class.

Essentially parse-server creates the _User in the _SCHEMA collection, but it doesn't default to locked down _metadata permissions — thus exposing the entire user base with a simple new Parse.Query("_User").find() query.

I propose that when the _User class is created, we lock it down automatically. If I have time I'll try and add a fix for this, but I thought I would highlight it asap to prevent any undue security issues with new apps using parse-server.

Activity

  1. changed the title [-]Default _metadata class permissions for _User[/-] [+]Security issue with default _User class permissions (new apps only)[/+] on Feb 12, 2016
  2. added
    type:bugImpaired feature or lacking behavior that is likely assumed
    on Feb 12, 2016
  3. drew-gross commented on Feb 12, 2016

    @drew-gross
    Contributor

    Thanks for the note! Fortunately this only affects new apps, so any migrated apps won't be vulnerable to new security issues. A PR would be very much appreciated :)

  4. flovilmart commented on Feb 15, 2016

    @flovilmart
    Contributor

    @drew-gross I can take care of that one too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:bugImpaired feature or lacking behavior that is likely assumed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions