POJIA破甲
地图 / Libcurl ocasionally sends HTTPS traffic to port 443 rather than specified port 8080

Libcurl ocasionally sends HTTPS traffic to port 443 rather than specified port 8080

信息泄露 / 信息泄露 / #637800

厂商
curl
严重程度
低危 · CVSS 5.3
赏金
—
弱点
信息泄露
研究员
@omdr
披露日期
2021-02-03
资产
https://github.com/curl/curl
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(3381 字符中的一小部分)
Summary: We have encountered an issue with libcurl where, under certain network conditions, the library will attempt to submit data to an incorrect port as was set by CURLOPT_PORT. As information is sent to an unauthorised port, we consider this an information disclosure issue.

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

时间线

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

同类报告

Confidential data of users and limited metadata of programs and reports accessible via GraphQLHackerOne · 2019-02-03Sensitive user information disclosure at bonjour.uber.com/marketplace/_rpc via the 'userUuid' parameterUber · 2019-09-09The /reports/:id.json endpoint discloses potentially sensitive user attributes when reporter summary is presentHackerOne · 2025-04-01Customer private program can disclose email any users through invited via usernameHackerOne · 2020-05-15 · $7,500Access to multiple production Grafana dashboardsSnapchat · 2020-11-04 · $10,000Open prod Jenkins instanceSnapchat · 2017-08-19 · $15,000