0x00 前言
CobaltStrike是一款知名的后渗透利用软件,集成了端口转发、服务扫描,自动化溢出,多模式端口监听等等强大的功能。CobaltStrike受到安全从业人员的广泛使用,无论是在攻防演练还是真实的攻击案例中都能够看到CobaltStrike的身影。因此站在安全研究者角度有必要对CobaltStrike进行深度分析。在本文中我们分别对Cobaltstrike 4.5的的认证过程、部分暗桩和默认特征进行了修改和分析。
0x01 认证破解
在没有破解之前可能这样的
破解之后可能是这样的
我们要先过他的认证,根据弹窗提示,直接全局搜索关键字 "cobaltstrike.auth"。
来到Authorization.java
public Authorization() {String var1 = CommonUtils.canonicalize("cobaltstrike.auth");if (!(new File(var1)).exists()) {try {File var2 = new File(this.getClass().getProtectionDomain().getCodeSource().getLocation().toURI());if (var2.getName().toLowerCase().endsWith(".jar")) {var2 = var2.getParentFile();}var1 = (new File(var2, "cobaltstrike.auth")).getAbsolutePath();} catch (Exception var22) {MudgeSanity.logException("trouble locating auth file", var22, false);}}byte[] var23 = CommonUtils.readFile(var1);if (var23.length == 0) {this.error = "Could not read " + var1;} else {AuthCrypto var3 = new AuthCrypto();byte[] var4 = var3.decrypt(var23);if (var4.length == 0) {this.error = var3.error();} else {try {DataParser var5 = new DataParser(var4);var5.big();int var6 = var5.readInt();this.watermark = var5.readInt();byte var7 = var5.readByte();if (var7 < 45) {this.error = "Authorization file is not for Cobalt Strike 4.5+";return;}这种情情况可以使用硬编码
byte[] var23 = {1, -55, -61, 127, 0, 1, -122, -96, 45, 16, 27, -27, -66, 82, -58, 37, 92, 51, 85, -114, -118, 28, -74, 103, -53, 6, 16, -128, -29, 42, 116, 32, 96, -72, -124, 65, -101, -96, -63, 113, -55, -86, 118, 16, -78, 13, 72, 122, -35, -44, 113, 52, 24, -14, -43, -93, -82, 2, -89, -96, 16, 58, 68, 37, 73, 15, 56, -102, -18, -61, 18, -67, -41, 88, -83, 43, -103, 16, 94, -104, 25, 74, 1, -58, -76, -113, -91, -126, -90, -87, -4, -69, -110, -42, 16, -13, -114, -77, -47, -93, 53, -78, 82, -75, -117, -62, -84, -34, -127, -75, 66, 0, 0, 0, 24, 66, 101, 117, 100, 116, 75, 103, 113, 110, 108, 109, 48, 82, 117, 118, 102, 43, 86, 89, 120, 117, 119, 61, 61};public Authorization() {String var1 = CommonUtils.canonicalize("cobaltstrike.auth");if (!(new File(var1)).exists()) {try {File var2 = new File(this.getClass().getProtectionDomain().getCodeSource().getLocation().toURI());if (var2.getName().toLowerCase().endsWith(".jar")) {var2 = var2.getParentFile();}var1 = (new File(var2, "cobaltstrike.auth")).getAbsolutePath();} catch (Exception var22) {MudgeSanity.logException("trouble locating auth file", var22, false);}}byte[] var23 = {1, -55, -61, 127, 0, 1, -122, -96, 45, 16, 27, -27, -66, 82, -58, 37, 92, 51, 85, -114, -118, 28, -74, 103, -53, 6, 16, -128, -29, 42, 116, 32, 96, -72, -124, 65, -101, -96, -63, 113, -55, -86, 118, 16, -78, 13, 72, 122, -35, -44, 113, 52, 24, -14, -43, -93, -82, 2, -89, -96, 16, 58, 68, 37, 73, 15, 56, -102, -18, -61, 18, -67, -41, 88, -83, 43, -103, 16, 94, -104, 25, 74, 1, -58, -76, -113, -91, -126, -90, -87, -4, -69, -110, -42, 16, -13, -114, -77, -47, -93, 53, -78, 82, -75, -117, -62, -84, -34, -127, -75, 66, 0, 0, 0, 24, 66, 101, 117, 100, 116, 75, 103, 113, 110, 108, 109, 48, 82, 117, 118, 102, 43, 86, 89, 120, 117, 119, 61, 61};if (var23.length == 0) {this.error = "Could not read " + var1;} else {AuthCrypto var3 = new AuthCrypto();byte[] var4 = var3.decrypt(var23);if (var4.length == 0) {this.error = var3.error();} else {try {DataParser var5 = new DataParser(var4);var5.big();int var6 = var5.readInt();this.watermark = var5.readInt();byte var7 = var5.readByte();if (var7 < 45) {this.error = "Authorization file is not for Cobalt Strike 4.5+";return;}我们修改文件之后发现依然启动不了cobaltstrike,没有加载出GUI,我们来看看aggressor.Aggressor都干了啥。
跟进checkGUI
跟进initializeStarter,发现exit函数,将其注释
跟进checkLicenseGUI发现isValid()、isPerpetual()、isExpired()、isAlmostExpired()对授权是否有效、授权是否过期进行判断
发现又回到了Authorization.java
跟进ConnectDialog,发现initialize继续跟进
发现退出函数,将它注释即可
破解完成 直接启动
0x02 暗桩
- javaagent命令行关键字检测
- 机器上线之后执行命令60秒自动退出
beacon/BeaconData中将shouldPad方法的值固定为false:this.shouldPad = false;
- 4个小时机器自动掉线
beacon/CommandBuilder中的.class判断
0x03 默认特征
Teamserver 登录流程分析
Teamserver启动时有这么一句话 "SHA256 hash of SSL cert is:"
我们直接全局搜索发现TeamServer.java,我们直接去看server/TeamServer.java
这里我们可以看到SecureServerSocket继续跟进
同时可以看到同样的 super.initializeStarter(this.getClass()); 校验
来到ssl/SecureServerSocket.java 这里会默认读48879的数据,作为默认值如不对此进行能修改,我们可以根据此信息对cobaltstrike进行爆破
ssl/SecureSocket.java
checksum8算法分析
checksum8算法的作用主要用于我们在上线时所请求的地址,虽然我们可以通过配置文件进行修改,但在原理上只是为其增加了一个uri,默认的依然可以接受原有的请求。
cloudstrike/WebServer.java
public static long checksum8(String text) {if (text.length() < 4) {return 0L;} else {text = text.replace("/", "");long sum = 0L;for(int x = 0; x < text.length(); ++x) {sum += (long)text.charAt(x);}return sum % 256L;}}
common/CommonUtils.java
watermark水印
common/ListenerConfig.java
beacon特征
beacon/BeaconPayload.java
beacon_obfuscate方法对beacon的配置信息进行了异或混淆,异或的key是固定的,3.x是0x69,4.x为0x2e(46的16进制),修改的同时对应dll文件也要进行修改
watermark水印
common/ListenerConfig.java
jarm指纹
通过改变TLS版本来改变指纹
测试结果
修改原版ua头
cobaltstrike 里的UA头都是比较老的UA,可以作为辅助识别cobaltstrike
在resources/ua.txt修改默认UA头。
0x04 关于我们
我们是源影安全实验室(MetaShadow-Lab),源影意为汇集全球海量源数据,同时与全网最新数据如影随形。在后续我们会推出一系列技术研究文章,欢迎关注,敬请期待。