POJIA破甲
地图 / No Rate Limiting On Phone Number Login Leads to Login Bypass

No Rate Limiting On Phone Number Login Leads to Login Bypass

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

厂商
Smule
严重程度
低危
赏金
—
弱点
认证缺陷(通用)
研究员
@done11
披露日期
2020-07-24
资产
*.smule.com
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(2932 字符中的一小部分)
A rate limiting algorithm is used to check if the user session has to be limited based on the information in the session cache. In case a client made too many requests within a given time frame.
原文中的代码
POST /user/json/phone_login HTTP/1.1
Host: web.smule.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Accept: application/json, text/plain, */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: https://web.smule.com/s/explore
Content-Type: …

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

时间线

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

同类报告

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