POJIA破甲
地图 / Excessive allocation of memory in tls_get_message_header() (CVE-2016-6307)

Excessive allocation of memory in tls_get_message_header() (CVE-2016-6307)

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

厂商
Internet Bug Bounty
严重程度
低危
赏金
—
弱点
资源消耗失控
研究员
@theyarestone
披露日期
2017-05-25
资产
OpenSSL (Legacy)
CVE
CVE-2016-6307

该报告还没有中文解读。

原文摘录

摘自原文(1996 字符中的一小部分)
A TLS message includes 3 bytes for its length in the header for the message. This would allow for messages up to 16Mb in length. Messages of this length are excessive and OpenSSL includes a check to ensure that a peer is sending reasonably sized messages in order to avoid too much memory being …

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

时间线

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

同类报告

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