POJIA破甲
地图 / Account takeover w/o interaction for a user that doesn't have 2fa enabled via 2fa linking and improper auth at /api/2fa/verify

Account takeover w/o interaction for a user that doesn't have 2fa enabled via 2fa linking and improper auth at /api/2fa/verify

身份认证 / 认证缺陷(通用) / #810880

厂商
Helium
严重程度
低危
赏金
—
弱点
认证缺陷(通用)
研究员
@w2w
披露日期
2020-07-26
资产
https://helium-console-dev.herokuapp.com/
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(1568 字符中的一小部分)
Description: Hello, team! I found 2 vulnerabilities in your 2FA implementation: 1) There is a possibility to link 2FA to any other account if it wasn't set up before and user ID is known on the request /api/2fa. In order to do this, after performing a request for 2FA linking, substitute the ID to …

默认不展示报告全文。以上为简短摘录,完整复现过程请阅读原文。版权归研究员与 Helium 所有。

时间线

  • 报告提交
  • 公开披露
阅读 HackerOne 原文 ↗作者 @w2w · 版权归作者与 Helium 所有

同类报告

Improper Authentication - any user can login as other user with otp/logout & otp/loginSnapchat · 2021-09-03Bypassing Digits origin validation which leads to account takeoverX / xAI · 2020-06-24Flickr Account Takeover using AWS Cognito APIFlickr · 2021-12-18Chained Bugs to Leak Victim's Uber's FB Oauth TokenUber · 2019-01-25[cs.money] Open Redirect Leads to Account TakeoverCS Money · 2020-09-30OTP token bypass in accessing user settingsRazer · — · $1,000
Account takeover w/o interaction for a user that doesn't have 2fa enabled via 2fa linking and improper auth at /api/2fa/verify · 破甲 POJIA