← 返回地图破甲

URL API: triple-slash parses path segment as hostname

其他弱点 / Use of Incorrectly-Resolved Name or Reference / #3923212

厂商
curl
严重程度
低危
赏金
—
弱点
Use of Incorrectly-Resolved Name or Reference
研究员
@thinhlx
披露日期
2026-08-07
资产
https://github.com/curl/curl
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(1390 字符中的一小部分)
libcurl's URL API misparses http:///host/path. Per RFC 3986, the authority between // and / is empty, so /host/path is the path. But parseurl() in lib/urlapi.c treats the first segment as the hostname. On line ~1087, the slash counter i reaches 3, which is within the valid 1-3 range, and hostp is …

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

时间线

阅读 HackerOne 原文 ↗作者 @thinhlx · 版权归作者与 curl 所有

同类报告

DNS domain search list followed for extant domain missing A or AAAA recordscurl · 2026-06-08Name collision of shared foldersNextcloud · 2023-04-29CVE-2026-8924: trailing dot domain super cookiecurl · 2026-06-24