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

fix: password reset flows should allow some cases with no primary user and ep user existing #941

Merged
merged 2 commits into from
Oct 10, 2024

Conversation

porcellus
Copy link
Collaborator

Summary of change

(A few sentences about this PR)

Related issues

  • Link to issue1 here
  • Link to issue1 here

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)

Documentation changes

(If relevant, please create a PR in our docs repo, or create a checklist here highlighting the necessary changes)

Checklist for important updates

  • Changelog has been updated
  • coreDriverInterfaceSupported.json file has been updated (if needed)
    • Along with the associated array in lib/ts/version.ts
  • frontendDriverInterfaceSupported.json file has been updated (if needed)
  • Changes to the version if needed
    • In package.json
    • In package-lock.json
    • In lib/ts/version.ts
  • Had run npm run build-pretty
  • Had installed and ran the pre-commit hook
  • If new thirdparty provider is added,
    • update switch statement in recipe/thirdparty/providers/configUtils.ts file, createProvider function.
    • add an icon on the user management dashboard.
  • Issue this PR against the latest non released version branch.
    • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
    • If no such branch exists, then create one from the latest released branch.
  • If have added a new web framework, update the add-ts-no-check.js file to include that
  • If added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (like someFunc: function () {..}).
  • If added a new recipe, then make sure to expose it inside the recipe folder present in the root of this repo. We also need to expose its types.
  • If added a new entry point, then make sure that it is importable by adding it to the exports in package.json

Remaining TODOs for this PR

  • Item1
  • Item2

Copy link

cloudflare-workers-and-pages bot commented Oct 9, 2024

Deploying supertokens-node-pr-check-for-edge-function-compat with  Cloudflare Pages  Cloudflare Pages

Latest commit: 64fdce3
Status: ✅  Deploy successful!
Preview URL: https://aea07b58.supertokens-node-b95.pages.dev

View logs


// If there is no existing primary user and there is a single option to link
// we see if that user can become primary (and a candidate for linking)
if (linkingCandidate === undefined && users.length === 1) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should also allow linking in case there is more than 1 user. Same way as the other function which picks the oldest user and tries to link with that. Ideallyt we just reuse that function

// If a primary user has the input email as verified or has no other emails: then it is always allowed to reset their password:
// - there is no risk of account takeover, because they have verified this email or haven't linked it to anything else
// - there will be no linking as a result of this action, so we do not need to check for linking.
// TODO: what happens if user M signs up with the email of the victim using a third-party provider that doesn't verify emails
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// TODO: what happens if user M signs up with the email of the victim using a third-party provider that doesn't verify emails

// extra security measure here to make sure that the input email in the primary user
// is verified, and if not, we need to make sure that there is no other email / phone number
// associated with the primary user account. If there is, then we do not proceed.

/*
This security measure helps prevent the following attack:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

move this comment above as well

);
}

if (!existingUser.isPrimaryUser) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove this if block

@porcellus porcellus merged commit 72e774f into 20.1 Oct 10, 2024
17 of 18 checks passed
@porcellus porcellus deleted the fix/password_reset_security_checks branch October 10, 2024 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants