POJIA破甲
地图 / Not using Binary::safe* functions for substr/strlen function

Not using Binary::safe* functions for substr/strlen function

其他弱点 / Unlabeled / #181315

厂商
Paragon Initiative Enterprises
严重程度
未评级
赏金
—
弱点
Unlabeled
研究员
@e3amn2l
披露日期
2016-11-13
资产
—
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(4075 字符中的一小部分)
Several places in the code don't use Binary::safe* or CryptoUtil::safe* functions, but use raw functions instead (strlen/substr) which can act as mb_funcname instead (not count bytes for strlen/etc...)
原文中的代码
            $lockTo = substr($lockTo, 0, strlen($lockTo) - 1);

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

时间线

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

同类报告

June 2022 Incident ReportHackerOne · 2022-07-01HTML-injection in PDF-export leads to LFIVisma Public · — · $500DOM XSS on duckduckgo.com searchDuckDuckGo · 2020-06-14An attacker can archive and unarchive any structured scope object on HackerOneHackerOne · 2022-04-18Java (Maven): Actually fix the use of insecure protocol to download/upload artifactsGitHub Security Lab · — · $4,000Handling of `tracking` command allows making arbitrary blind requests with user's cookies from Grammarly Extension's originSuperhuman (formerly Grammarly) · 2019-08-01