Skip to content

Latest commit

 

History

History
122 lines (105 loc) · 5.57 KB

README.md

File metadata and controls

122 lines (105 loc) · 5.57 KB

源工具链接:https://github.com/rabbitmask/WeblogicScan

weblogicScaner

简体中文 | English

截至 2020 年 11 月 27 日,weblogic 漏洞扫描工具。若存在未记录且已公开 POC 的漏洞,欢迎提交 issue。

原作者已经收集得比较完整了,在这里做了部分的 bug 修复,部分脚本 POC 未生效,配置错误等问题。之前查了一下发现部分 POC 无法使用。在这个项目里面对脚本做了一些修改,提高准确率。

注意:部分漏洞由于稳定性原因需要多次测试才可验证

目前可检测漏洞编号有(部分非原理检测,需手动验证):

  • weblogic administrator console
  • CVE-2014-4210
  • CVE-2016-0638
  • CVE-2016-3510
  • CVE-2017-3248
  • CVE-2017-3506
  • CVE-2017-10271
  • CVE-2018-2628
  • CVE-2018-2893
  • CVE-2018-2894
  • CVE-2018-3191
  • CVE-2018-3245
  • CVE-2018-3252
  • CVE-2019-2618
  • CVE-2019-2725
  • CVE-2019-2729
  • CVE-2019-2890
  • CVE-2020-2551
  • CVE-2020-14882
  • CVE-2020-14883

快速开始

依赖

  • python >= 3.6

进入项目目录,使用以下命令安装依赖库

$ pip3 install requests

使用说明

usage: ws.py [-h] -t TARGETS [TARGETS ...] -v VULNERABILITY
             [VULNERABILITY ...] [-o OUTPUT]

optional arguments:
  -h, --help            帮助信息
  -t TARGETS [TARGETS ...], --targets TARGETS [TARGETS ...]
                        直接填入目标或文件列表(默认使用端口7001). 例子:
                        127.0.0.1:7001
  -v VULNERABILITY [VULNERABILITY ...], --vulnerability VULNERABILITY [VULNERABILITY ...]
                        漏洞名称或CVE编号,例子:"weblogic administrator console"
  -o OUTPUT, --output OUTPUT
                        输出 json 结果的路径。默认不输出结果
  -s, --ssl             强制使用 https 协议请求

结果样例

(venv) ~/weblogicScanner$ python ws.py -t 192.168.124.129
[23:03:04][INFO] [*][Weblogic Console][192.168.56.129:7001] Start...
[23:03:04][INFO] [+][Weblogic Console][192.168.56.129:7001] Found module!
[23:03:04][INFO] [*][Weblogic Console][192.168.56.129:7001] Please verify manually!
[23:03:04][INFO] [*][CVE-2014-4210][192.168.56.129:7001] Start...
[23:03:04][INFO] [-][CVE-2014-4210][192.168.56.129:7001] Not found.
[23:03:04][INFO] [*][CVE-2016-0638][192.168.56.129:7001] Start...
[23:03:06][INFO] [-][CVE-2016-0638][192.168.56.129:7001] Not vulnerability.
[23:03:06][INFO] [*][CVE-2016-3510][192.168.56.129:7001] Start...
[23:03:08][INFO] [-][CVE-2016-3510][192.168.56.129:7001] Not vulnerability.
[23:03:08][INFO] [*][CVE-2017-3248][192.168.56.129:7001] Start...
[23:03:10][INFO] [-][CVE-2017-3248][192.168.56.129:7001] Not vulnerability.
[23:03:10][INFO] [*][CVE-2017-3506][192.168.56.129:7001] Start...
[23:03:10][INFO] [-][CVE-2017-3506][192.168.56.129:7001] Not vulnerability.
[23:03:10][INFO] [*][CVE-2017-10271][192.168.56.129:7001] Start...
[23:03:10][INFO] [-][CVE-2017-10271][192.168.56.129:7001] Not vulnerability.
[23:03:10][INFO] [*][CVE-2018-2628][192.168.56.129:7001] Start...
[23:03:14][INFO] [+][CVE-2018-2628][192.168.56.129:7001] Exists vulnerability!
[23:03:14][INFO] [*][CVE-2018-2893][192.168.56.129:7001] Start...
[23:03:18][INFO] [+][CVE-2018-2893][192.168.56.129:7001] Exists vulnerability!
[23:03:18][INFO] [*][CVE-2018-2894][192.168.56.129:7001] Start...
[23:03:19][INFO] [+][CVE-2018-2894][192.168.56.129:7001] Found module!
[23:03:19][INFO] [*][CVE-2018-2894][192.168.56.129:7001] Please verify manually!
[23:03:19][INFO] [*][CVE-2018-3191][192.168.56.129:7001] Start...
[23:03:23][INFO] [+][CVE-2018-3191][192.168.56.129:7001] Exists vulnerability!
[23:03:23][INFO] [*][CVE-2018-3245][192.168.56.129:7001] Start...
[23:03:29][INFO] [-][CVE-2018-3245][192.168.56.129:7001] Not vulnerability.
[23:03:29][INFO] [*][CVE-2018-3252][192.168.56.129:7001] Start...
[23:03:36][INFO] [+][CVE-2018-3252][192.168.56.129:7001] Found module!
[23:03:36][INFO] [*][CVE-2018-3252][192.168.56.129:7001] Please verify manually!
[23:03:36][INFO] [*][CVE-2019-2618][192.168.56.129:7001] Start...
[23:03:36][INFO] [+][CVE-2019-2618][192.168.56.129:7001] Found module!
[23:03:36][INFO] [*][CVE-2019-2618][192.168.56.129:7001] Please verify manually!
[23:03:36][INFO] [*][CVE-2019-2725][192.168.56.129:7001] Start...
[23:03:46][INFO] [-][CVE-2019-2725][192.168.56.129:7001] Not vulnerability.
[23:03:46][INFO] [*][CVE-2019-2729][192.168.56.129:7001] Start...
[23:03:54][INFO] [-][CVE-2019-2729][192.168.56.129:7001] Not vulnerability.
[23:03:54][INFO] [*][CVE-2019-2888][192.168.56.129:7001] Start...
[23:03:56][INFO] [+][CVE-2019-2888][192.168.56.129:7001] Found module!
[23:03:56][INFO] [*][CVE-2019-2888][192.168.56.129:7001] Please verify manually!
[23:03:56][INFO] [*][CVE-2019-2890][192.168.56.129:7001] Start...
[23:03:58][INFO] [-][CVE-2019-2890][192.168.56.129:7001] Not vulnerability.
[23:03:58][INFO] [*][CVE-2020-2551][192.168.56.129:7001] Start...
[23:03:58][INFO] [+][CVE-2020-2551][192.168.56.129:7001] Found module!
[23:03:58][INFO] [*][CVE-2020-2551][192.168.56.129:7001] Please verify manually!
[23:03:58][INFO] [*][CVE-2020-2555][192.168.56.129:7001] Start...
[23:04:02][INFO] [+][CVE-2020-2555][192.168.56.129:7001] Exists vulnerability!
[23:04:02][INFO] [*][CVE-2020-2883][192.168.56.129:7001] Start...
[23:04:06][INFO] [+][CVE-2020-2883][192.168.56.129:7001] Exists vulnerability!
[23:04:06][INFO] [*][CVE-2020-14882][192.168.56.129:7001] Start...
[23:04:23][INFO] [-][CVE-2020-14882][192.168.56.129:7001] Not vulnerability.
[23:04:23][INFO] [*][CVE-2020-14883][192.168.56.129:7001] Start...
[23:04:23][INFO] [+][CVE-2020-14883][192.168.56.129:7001] Exists vulnerability!