POJIA破甲
地图 / SOCKS5 no-auth accepted despite username/password-only authentication

SOCKS5 no-auth accepted despite username/password-only authentication

身份认证 / 认证缺陷(通用) / #3786077

厂商
curl
严重程度
低危
赏金
—
弱点
认证缺陷(通用)
研究员
@kalfkinen
披露日期
2026-06-09
资产
https://github.com/curl/curl
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(4925 字符中的一小部分)
curl/libcurl appears to allow unauthenticated SOCKS5 negotiation even when the caller explicitly configures username/password-only SOCKS5 authentication. With `--socks5-basic` and SOCKS5 credentials set, curl still advertises both SOCKS5 method `0x00` (no authentication) and `0x02` …
原文中的代码
Repository: https://github.com/curl/curl.git
Commit: d3e9a815c4a68099b774742073c50b996d69fcd6
Commit date: 2026-06-05T16:57:38+02:00
Commit subject: tidy-up: miscellaneous

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

时间线

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

同类报告

Improper Authentication - any user can login as other user with otp/logout & otp/loginSnapchat · 2021-09-03Bypassing Digits origin validation which leads to account takeoverX / xAI · 2020-06-24Flickr Account Takeover using AWS Cognito APIFlickr · 2021-12-18Chained Bugs to Leak Victim's Uber's FB Oauth TokenUber · 2019-01-25[cs.money] Open Redirect Leads to Account TakeoverCS Money · 2020-09-30OTP token bypass in accessing user settingsRazer · — · $1,000