curl cross-origin HTTPS redirect reuses TLS client certificate for unintended second-origin mTLS authentication
该报告还没有中文解读。
原文摘录
摘自原文(12233 字符中的一小部分)
Summary: When curl follows an HTTPS redirect to a different origin under normal `-L` / `CURLOPT_FOLLOWLOCATION` behavior, it still presents the configured TLS client certificate to the redirected-to HTTPS server. This happens without `--location-trusted` / `CURLOPT_UNRESTRICTED_AUTH`, even though …
原文中的代码
set -euo pipefail
ROOT="$PWD"
CURL_BIN="$ROOT/src/.libs/curl"
if [ ! -x "$CURL_BIN" ]; then
echo "expected a built curl binary at $CURL_BIN" >&2
exit 1
fi
command -v python3 >/dev/null 2>&1 || {
echo "python3 is required" >&2
exit 1
}
command -v openssl >/dev/null 2>&1 || {
echo …默认不展示报告全文。以上为简短摘录,完整复现过程请阅读原文。版权归研究员与 curl 所有。
时间线
- 报告提交
- 公开披露
阅读 HackerOne 原文 ↗作者 @fanhua · 版权归作者与 curl 所有