Skip to content
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.

Enumeration of registered email addresses via user profile API #38

Open
sveeke opened this issue Jun 18, 2018 · 2 comments
Open

Enumeration of registered email addresses via user profile API #38

sveeke opened this issue Jun 18, 2018 · 2 comments
Labels
bug-infoleak risk-moderate Security issues with a moderate impact
Milestone

Comments

@sveeke
Copy link
Contributor

sveeke commented Jun 18, 2018

BadgeUserProfile uses BadgeUserProfileSerializer which responds to registration attempts with this error message:

Account could not be created. An account with this email address may already exist.

This API endpoint can be accessed by sending a POST request to v1/user/profile. It expects these fields as parameters:

first_name = serializers.CharField(max_length=30, allow_blank=True)                
last_name = serializers.CharField(max_length=30, allow_blank=True)                 
email = serializers.EmailField()                                                   
password = serializers.CharField(style={'input_type': 'password'}, write_only=True)
@sveeke sveeke added risk-moderate Security issues with a moderate impact bug-infoleak labels Jun 18, 2018
@sveeke sveeke added this to the Pilot 2018 milestone Jun 18, 2018
@ottonomy
Copy link

This is a valid issue. There may be some potential for data leak. The account cannot be created, so some error message must be returned. It is possible to be even less specific in the error message trading off protection against this potential data leak for a more confusing user experience.

@sveeke
Copy link
Contributor Author

sveeke commented Jan 17, 2019

@ottonomy has something been changed in Badgr because of this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug-infoleak risk-moderate Security issues with a moderate impact
Projects
None yet
Development

No branches or pull requests

2 participants