v 友帮忙分析下这次 https 劫持

V2EX = way to explore

V2EX 是一个关于分享和探索的地方

现在注册

已注册用户请登录

这是一个创建于 862 天前的主题，其中的信息可能已经有所发展或是发生改变。

这是在 k8s 的某个 pod 里面执行的 curl 命令，然后被劫持到了 http://144.dragonparking.com

而且是偶发的，有段时间会劫持有段时间就正常

宿主机上执行 curl 没出现过劫持

这个是怎么实现的

以下是劫持返回的 html

<html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>tencentcloudapi.com</title> <meta http-equiv="Content-Type" cOntent="text/html; charset="/> <script type='text/Javascript' language='Javascript'> var domain = 'tencentcloudapi.com'; var uniqueTrackingID = 'MTY4NTU3OTcwNi4xODgzOmZlODk3NWU3ODcyMjg1MDg2YWNlZGU1NTM5YWZlMTBmNDFmMWQyYzIzZTQ5MGY0OTA2MDE1ZTViN2I3ZDEwYTU6NjQ3N2U3YmEyZGZiOA=='; var clickTracking = false; var themedata = ''; var xkw = ''; var xsearch = ''; var xpcat = ''; var bucket = ''; var clientID = ''; var clientIDs = ''; var num_ads = 0; var adtest = 'off'; var scriptPath = ''; </script> <script src='http://www.v2ex.com//d38psrni17bvxu.cloudfront.net/scripts/js3.js' type='text/Javascript' language='Javascript'></script>

 </head> <body> <script type="text/Javascript">var ls = function(xhr, path, token) { xhr.Onreadystatechange= function () { if (xhr.readyState === XMLHttpRequest.DONE) { if (xhr.status >= 200 && xhr.status <= 400) { if (xhr.responseText.trim() === '') { return; } console.log(JSON.parse(xhr.responseText)) } else { console.log('There was a problem with the request.'); } } } xhr.open('GET', path + '/ls.p' + 'hp?t=6477e7ba&token=' + encodeURI(token), true); xhr.send();

}; ls(new XMLHttpRequest(), scriptPath, '098d33e1ee92577488c3f7c512742c23d15f6952');</script> <script type='text/Javascript' language='Javascript'> window.Onload= function() { if(clickTracking && typeof track_Onclick== 'function') track_onclick("8738cf3b6b543a07139579dbbd0fc3fa531854b6"); top.location.href = "http://144.dragonparking.com/?site=tencentcloudapi.com&t=1685579706&s=26356433e9449717b0e51e87ffb4349a&fs=http%3A%2F%2Fc.parkingcrew.net%2F%3Fdomain_name%3Dtencentcloudapi.com"; }; </script> </body>

</html>

2 条回复 2023-06-02 16:20:20 +08:00

ysc3839

2023-06-02 13:10:26 +08:00 via Android

建议宿主机抓包看看

quxuanxuan

2023-06-02 16:20:20 +08:00

@ysc3839 找到原因了，是 dns 解析的问题，搜索域底下可以解析这个域名