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

Reset Password API should return success response even if email doesn't exist #5277

Closed
5 tasks done
anhcuky opened this issue Dec 20, 2024 · 2 comments
Closed
5 tasks done
Labels
enhancement New feature or request

Comments

@anhcuky
Copy link
Contributor

anhcuky commented Dec 20, 2024

Requirements

  • Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a feature request? Do not put multiple feature requests in one issue.
  • Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
  • Do you agree to follow the rules in our Code of Conduct?

Is your proposal related to a problem?

I notice that the Reset Password returns 401 incorrect_login if the requested email doesn't exist. This way someone can check if my email was used for registration, not ideal especially for NSFW instances.

Describe the solution you'd like.

Always return the same success message regardless if the email exists or not

Describe alternatives you've considered.

.

Additional context

No response

@anhcuky anhcuky added the enhancement New feature or request label Dec 20, 2024
@Nothing4You
Copy link
Collaborator

there are several other ways to determine this as well:

  • try to sign up with an email address
  • try to change your account email to another one

a common pattern for the reset message is something like "reset instructions have been sent if an account using the provided email address exists".

@phiresky
Copy link
Collaborator

We've had some discussions about this before somewhere on Github. It may be true that we have other endpoints that allow this as well, but even if we don't prioritize fixing all of them we can still slowly move (updated / new code) towards a more secure pattern here - as long as everyone agrees the UX cost is okay.

@anhcuky anhcuky closed this as completed Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants