POJIA破甲
地图 / SSRF via maliciously crafted URL due to host confusion

SSRF via maliciously crafted URL due to host confusion

服务端请求伪造 / SSRF / #704621

厂商
curl
严重程度
高危 · CVSS 10
赏金
—
弱点
SSRF
研究员
@jlleitschuh
披露日期
2021-01-08
资产
https://github.com/curl/curl
CVE
CVE-2018-3774

该报告还没有中文解读。

原文摘录

摘自原文(1832 字符中的一小部分)
Curl is vulnerable to SSRF due to improperly parsing the host component of the URL compared to other URL parsers and the [URL living standard](https://url.spec.whatwg.org/).
原文中的代码
const whatwg_url = require('whatwg-url'); // Created by the RFC maintainers

const theUrl = new whatwg_url.URL("https://google.com:80\\\\@yahoo.com/");
const theUrl2 = new whatwg_url.URL("https://google.com:80\\@yahoo.com/");

const nodeUrl = new URL("https://google.com:80\\\\@yahoo.com/");
const …

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

时间线

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

同类报告

SSRF in Exchange leads to ROOT access in all instancesShopify · 2018-05-23Server Side Request Forgery (SSRF) via Analytics ReportsHackerOne · 2023-12-08 · $25,000Server-Side Request Forgery using Javascript allows to exfill data from Google MetadataSnapchat · 2020-11-30Server Side Request Forgery (SSRF) at app.hellosign.com leads to AWS private keys disclosureDropbox · — · $4,913SSRF on project import via the remote_attachment_url on a NoteGitLab · 2020-06-07 · $10,000Server Side Request Forgery mitigation bypassGitLab · 2020-04-18