Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

No confirmation email sent to user after a successful password reset

未关闭 适合新手
#928 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
72/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
typescript

调研方向

阅读 application/backend/src/controllers/UsersController.ts,重点关注 resetPassword 以及 generatePasswordResetLink 如何发送电子邮件。在进行更改前,检查现有的邮件发送模式和相关测试。完成标准是:重置成功后向用户当前的电子邮件地址发送确认邮件,并且测试覆盖此行为。

由索引模型根据 Issue 内容生成。

描述

backend bug Notifications

UsersController.resetPassword in application/backend/src/controllers/UsersController.ts validates the reset token, updates the user's password hash, and marks the token as used. but no confirmation email goes out to the user after the reset completes. generatePasswordResetLink sends the initial reset link, but once the user clicks the link and submits a new password, nothing lands in their inbox.

Risk: the user has no way to detect a password reset that wasn't triggered by them. If someone managed to trigger a reset on their account (e.g. by intercepting an already-issued reset link etc), the legitimate user gets no signal until they try to log in with their old password and fail.

Google, Auth0 and most modern SaaS platforms send a "your password was changed" email on every successful reset specifically to catch this class of attack early.

Suggested fix: at the end of resetPassword, after the password hash is written and the token is marked used, send a confirmation email to the user's current email address ("Your CTRL password was changed. If this wasn't you, contact support.").

主要语言
TypeScript
星标
4
派生
0
平均合并
14 小时 50 分钟
30 天内合并 PR
5

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Garvan-Data-Science-Platform/ctrl 的其他 Issue

查看 Garvan-Data-Science-Platform/ctrl 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。