POJIA破甲
地图 / a very long name in hey.com can prevent anyone from accessing their contacts and probably can cause denial of service

a very long name in hey.com can prevent anyone from accessing their contacts and probably can cause denial of service

拒绝服务 / 资源消耗失控 / #1018037

厂商
Basecamp
严重程度
中危
赏金
$1,000
弱点
资源消耗失控
研究员
@tw4v3sx
披露日期
2020-11-10
资产
*.hey.com
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(1991 字符中的一小部分)
Summary : ========= after trying to change my initial name to something long i found out that their are no limits to how long it can be , so i directly changed it to something very long {F1050497} which caused my account to really slow down when accessing it and in **the android app , it just keeps …

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

时间线

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

同类报告

DoS on PayPal via web cache poisoningPayPal · 2019-10-23 · $9,700profile-picture name parameter with large value lead to DoS for other users and programs on the platformHackerOne · 2020-03-25Denial of service to WP-JSON API by cache poisoning the CORS allow origin headerAutomattic · 2020-04-16[Urgent] Invalidating OAuth2 Bearer token makes TweetDeck unavailableX / xAI · 2019-04-25Oracle Webcenter Sites administrative and hi-privilege access available directly from the internet (/cs/Satellite)LocalTapiola · — · $18,000Denial of service via cache poisoningHackerOne · 2018-12-22 · $2,500