优雅地寻找网站源码(一)

扫码领资料

获网安教程

# 优雅地寻找网站源码(一) ## 0x0 前言 渗透过程中如果能获取到网站的源代码，那么无疑开启了上帝视角。虽然之前出现过不少通过搜索引擎查找同类网站，然后批量扫备份的思路，但是却没...

文章来源: https://forum.butian.net/share/358文章作者：xq17如有侵权请您联系我们，我们会进行删除并致歉

优雅地寻找网站源码(一)

0x0 前言

渗透过程中如果能获取到网站的源代码，那么无疑开启了上帝视角。虽然之前出现过不少通过搜索引擎查找同类网站，然后批量扫备份的思路，但是却没人分享其具体过程，这里笔者便整理了自己开发分布式扫描器的目录扫描模块的一些尝试的思路，同时分享一些寻找源码的其他手段，希望能给读者带来一些新的体验。

0x1 搜索技巧

0x1.1 代码托管平台

国外的github和国内的gitee都是第三方代码托管平台，通过一些搜索技巧，我们可以从中发现很多泄露的敏感信息，其中就包括一些程序的源代码。

这里笔者对码云平时用的不多，故对此只是简单提提，下面，则重点介绍github的用法:

学习这个用法就我个人而言最大的好处是，遇到返回大量数据的时候，可以根据一些特点来过滤掉一些垃圾数据。

Github的搜索页面: 

    https://github.com/search

(1) quick cheat sheet

基础查询:

filename:config.php dbpasswd
filename:.bashrc password
shodan_api_key language:python
path:sites datab ases password
"baidu.com" ssh language:yaml
filename:file.php admin in:path
org:companyname "AWS_ACCESS_KEY_ID:"

git clone https://github.com/obheda12/GitDorker.git
cd GitDorker
docker build -t gitdorker .
docker run -it gitdorker
docker run -it -v $(pwd)/tf:/tf gitdorker -tf tf/TOKENSFILE -q tesla.com -d dorks/DORKFILE -o tesla
docker run -it -v $(pwd)/tf:/tf xshuden/gitdorker -tf tf/TOKENSFILE -q tesla.com -d dorks/DORKFILE -o tesla

免安装使用:

python3 GitDorker.py -tf ./TF/TOKENSFILE -q ximalaya.com -d ./Dorks/alldorksv3 -o x mly

0x1.2 搜索引擎

Google:

XX源码
XX完整包
xx安装程序
xx备份
xx代码
xx开源
xx源程序
xx框架
xx ext:rar | ext:tar.gz |ext:zip

0x1.3 网盘搜索

0x2 曲线思路

0x2.1 提取特征

0x2.2 资产收集

0x2.3 简单fuzz

0x2.4 编写nuclei插件

id: back-up-files

info:
  name: Find Resource Code Of Target Template
  author: xq17
  severity: medium
  tags: exposure,backup

1.HTTP Requests start with a request block which specifies the start of the requests for the template.

2.Request method can be GET, POST, PUT, DELETE, etc depending on the needs.

3.Redirection conditions can be specified per each template. By default, redirects are not followed. However, if desired, they can be enabled with redirects: true in request d etails.

4.The next part of the requests is the path of the request path. Dynamic variables can be placed in the path to modify its behavior on runtime.

Variables start with {{ and end with }} and are case-sensitive.

{{b aseURL}} - This will replace on runtime in the request by the original URL as specified in the target file.

{{Hostname}} - Hostname variable is replaced by the hostname of the target on runtime.

5.Headers can also be specified to be sent along with the requests. Headers are placed in form of key/value pairs. An example header configuration looks like this:

# headers contains the headers for the request
headers:
 # Custom user-agent header
 User-Agent: Some-Random-User-Agent
 # Custom request origin
 Origin: https://google.com

6.Body specifies a body to be sent along with the request. (发送POST包需要用到)

7.To maintain cookie b ased browser like session between multiple requests, you can simply use cookie-reuse: true in your template, Useful in cases where you want to maintain session between series of request to complete the exploit chain and to perform authenticated scans.(Session重用，作用是串联攻击链，实现登录验证再攻击)

# cookie-reuse accepts boolean input and false as default
cookie-reuse: true

8.Request condition allows to check for condition between multiple requests for writing complex checks and exploits involving multiple HTTP request to complete the exploit chain.

with DSL matcher, it can be utilized by adding req-condition: true and numbers as suffix with respective attributes, status_code_1, status_code_3, andbody_2 for example.(编写复杂攻击链)

  req-condition: true
   matchers:
     - type: dsl
       dsl:
         - "status_code_1 == 404 && status_code_2 == 200 && contains((body_2), 'secret_string')"

...还有许多高级用法比如支持raw http，race之类的，但是这里用不上，文档这个东西，够用就行。

requests:
  - method: GET
    path:
    - "{{b aseURL}}/wwwroot.zip"
    - "{{b aseURL}}/www.zip"

编写插件的第三步: 判断返回内容

Multiple matchers can be specified in a request. There are basically 6 types of matchers:

status(状态码) size(返回包大小) word(字符串) regex(正则匹配) binary(二进制文件)

还有一个dsl，高度自定义验证返回内容，可以对返回内容做一些操作(这里暂时用不上)

可用的辅助函数: https://nuclei.projectdiscovery.io/templating-guide/helper-functions/,

对于words and regexes,可以对返回内容的多个匹配条件用AND或OR进行组合。

Multiple words and regexes can be specified in a single matcher and can be configured with different conditions like AND and OR

可以对返回的包，选定match的区域，默认是body，也支持选择header等任意地方。

Multiple parts of the response can also be matched for the request, default matched part is body if not defined.

支持对条件取反，这个就是反证法的妙处了。

All types of matchers also support negative conditions, mostly useful when you look for a match with an exclusions. This can be used by adding negative: true in the matchers block.

支持使用多个matchers

Multiple matchers can be used in a single template to fingerprint multiple conditions with a single request.

支持matchers-condition

While using multiple matchers the default condition is to follow OR operation in between all the matchers, AND operation can be used to make sure return the result if all matchers returns true.

    matchers-condition: and
    matchers:
      - type: binary
        binary:
          - "504B0304"  # zip
        part: body
      - type: dsl
        dsl:
          - "len(body)>0"
      - type: status
        status:
          - 200

id: back-up-files

info:
  name: Find Resource Code Of Target Template
  author: xq17
  severity: medium
  tags: exposure,backup

requests:
  - method: GET
    path:
    - "{{b aseURL}}/wwwroot.zip"
    - "{{b aseURL}}/www.zip"
    matchers-condition: and
    matchers:
      - type: binary
        binary:
          - "504B0304"  # zip
        part: body
      - type: dsl
        dsl:
          - "len(body)>0"
      - type: status
        status:
          - 200

0x2.5 测试插件

本地起一个靶机，进行调试:

python3 -m http.server 9091

然后调试:

echo 'http://127.0.0.1:9091' | nuclei -t back-up-files.yaml -debug -timeout 2 -stats -proxy-url http://127.0.0.1:8080/

发包过程:

可以看到nuclei应用上插件之后，可以快速Fuzz出网站备份文件。

0x3 总结

第一篇主要是介绍了一些思路和nuclei插件编写简单思路，用于帮助新手快速入门，第二篇则是关于如何增强该插件，增加扫描目录列表，更精确的判断返回值等内容(这里建议读者，可以先自行阅读下nuclei-template的文档，这样学习效果更佳!),第三篇则是运用前两篇的知识点和增强型插件，来完成一次真实的寻找网站源码之旅。

声明：⽂中所涉及的技术、思路和⼯具仅供以安全为⽬的的学习交流使⽤，任何⼈不得将其⽤于⾮法⽤途以及盈利等⽬的，否则后果⾃⾏承担。