POJIA破甲
地图 / fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect

fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect

错误配置 / 违反安全设计原则(按标题归类) / #2377760

厂商
Node.js
严重程度
未评级
赏金
—
弱点
违反安全设计原则(按标题归类)
研究员
@uzlopak
披露日期
2024-05-03
资产
https://github.com/nodejs/node
CVE
CVE-2024-30261

该报告还没有中文解读。

原文摘录

摘自原文(2165 字符中的一小部分)
__A potential solution is attached as 0001-improve-bytesMatch.patch__
原文中的代码
aras@aras-Lenovo-Legion-5-17ARH05H:~/workspace/undici$ node benchmarks/bytesMatch.mjs 
cpu: AMD Ryzen 7 4800H with Radeon Graphics
runtime: node v21.6.2 (x64-linux)

benchmark                                    time (avg)             (min … max)       p75       p99      p999 …

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

时间线

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

同类报告

Bruteforce password recovery codeBumble · 2020-01-18Account creation with invalid email addresses / email is accepting % and %0d%0a line termination charsHackerOne · 2024-02-04 · $3,750Hacker.One Subdomain TakeoverHackerOne · 2016-09-20Stealing contact form data on www.hackerone.com using Marketo Forms XSS with postMessage frame-jumping and jQuery-JSONPHackerOne · 2017-08-29Unrestricted file upload in www.semrush.com > /my_reports/api/v1/upload/imageSemrush · 2020-01-10[Critical] Delete any accountOLX · —
fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect · 破甲 POJIA