186 lines
6.2 KiB
Markdown
186 lines
6.2 KiB
Markdown
## afrog <https://github.com/zan8in/afrog>
|
||
<!--auto_detail_badge_begin_0b490ffb61b26b45de3ea5d7dd8a582e-->
|
||
|
||
|
||
|
||
|
||
|
||
<!--auto_detail_badge_end_fef74f2d7ea73fcc43ff78e05b1e7451-->
|
||
|
||
## What is afrog
|
||
|
||
afrog is a high-performance vulnerability scanner that is fast and stable. It supports user-defined PoC and comes with several built-in types, such as CVE, CNVD, default passwords, information disclosure, fingerprint identification, unauthorized access, arbitrary file reading, and command execution. With afrog, network security professionals can quickly validate and remediate vulnerabilities, which helps to enhance their security defense capabilities.
|
||
|
||
## Features
|
||
|
||
* [x] Open source
|
||
* [x] Fast, stable, with low false positives
|
||
* [x] Detailed HTML vulnerability reports
|
||
* [x] Customizable and stably updatable PoCs
|
||
* [x] Active community exchange group
|
||
|
||
## Installation
|
||
|
||
### Prerequisites
|
||
|
||
- [Go](https://go.dev/) version 1.19 or higher.
|
||
|
||
you can install it with:
|
||
|
||
**Binary**
|
||
```sh
|
||
$ https://github.com/zan8in/afrog/releases
|
||
```
|
||
|
||
**Github**
|
||
```sh
|
||
$ git clone https://github.com/zan8in/afrog.git
|
||
$ cd afrog
|
||
$ go build cmd/afrog/main.go
|
||
$ ./afrog -h
|
||
```
|
||
|
||
**Go**
|
||
```sh
|
||
$ go install -v https://github.com/zan8in/afrog/cmd/afrog@latest
|
||
```
|
||
|
||
## Running afrog
|
||
|
||
By default, afrog scans all built-in PoCs, and if it finds any vulnerabilities, it automatically creates an HTML report with the date of the scan as the filename.
|
||
|
||
```sh
|
||
afrog -t https://example.com
|
||
```
|
||
|
||
**Warning occurs when running afrog**
|
||
|
||
If you see an error message saying:
|
||
```
|
||
[ERR] ceye reverse service not set: /home/afrog/.config/afrog/afrog-config.yaml
|
||
```
|
||
it means you need to modify the [configuration file](#configuration-file).
|
||
|
||
To execute a custom PoC directory, you can use the following command:
|
||
|
||
```sh
|
||
afrog -t https://example.com -P mypocs/
|
||
```
|
||
|
||
Use the command `-s keyword` to perform a fuzzy search on all PoCs and scan the search results. Multiple keywords can be used, separated by commas. For example: `-s weblogic,jboss`.
|
||
|
||
```sh
|
||
afrog -t https://example.com -s weblogic,jboss
|
||
```
|
||
|
||
Use the command `-S keyword` to scan vulnerabilities based on their severity level. Severity levels include: `info`, `low`, `medium`, `high`, and `critical`. For example, to only scan high and critical vulnerabilities, use the command `-S high,critical`.
|
||
|
||
```sh
|
||
afrog -t https://example.com -S high,critical
|
||
```
|
||
|
||
You can scan multiple URLs at the same time as well.
|
||
|
||
```sh
|
||
afrog -T urls.txt
|
||
```
|
||
|
||
## Configuration file
|
||
|
||
The first time you start afrog, it will automatically create a configuration file called `afrog-config.yaml`, which will be saved in the current user directory under `$HOME/.config/afrog/afrog-config.yaml`.
|
||
|
||
Here is an example config file:
|
||
|
||
```yaml
|
||
reverse:
|
||
ceye:
|
||
api-key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
|
||
domain: "xxxxxx.ceye.io"
|
||
```
|
||
|
||
`reverse` is a reverse connection platform used to verify command execution vulnerabilities that cannot be echoed back. Currently, only ceye can be used for verification. To obtain ceye, follow these steps:
|
||
|
||
- Go to the [ceye.io](http://ceye.io/) website and register an account.
|
||
- Log in and go to the personal settings page.
|
||
- Copy the `domain` and `api-key` and correctly configure them in the `afrog-config.yaml` file.
|
||
|
||
|
||
## Json Output (For developers)
|
||
|
||
### Json
|
||
Optional command: `-json` `-j`, Save the scan results to a JSON file. The JSON file includes the following contents by default: `target`, `fulltarget`, `id`, and `info`. The info field includes the following sub-fields: `name`, `author`, `severity`, `description`, and `reference`. If you want to save both `request` and `response` contents, please use the [-json-all](#jsonall) command parameter.
|
||
|
||
```sh
|
||
afrog -t https://example.com -json result.json
|
||
afrog -t https://example.com -j result.json
|
||
```
|
||
|
||
::: warning
|
||
The content of the JSON file is updated in real time. However, there is an important note to keep in mind: before the scan is completed, if developers want to parse the file content, they need to add a '`]`' symbol to the end of the file by themselves, otherwise it will cause parsing errors. Of course, if you wait for the scan to complete before parsing the file, this issue will not occur.
|
||
:::
|
||
|
||
|
||
### JsonAll
|
||
|
||
Optional command: `-json-all` `-ja`, The only difference between the `-json-all` and `-json` commands is that `-json-all` writes all vulnerability results, including `request` and `response`, to a JSON file.
|
||
|
||
```sh
|
||
afrog -t https://example.com -json-all result.json
|
||
afrog -t https://example.com -ja result.json
|
||
```
|
||
|
||
|
||
## Screenshot
|
||
|
||
|
||
|
||
<!--auto_detail_active_begin_e1c6fb434b6f0baf6912c7a1934f772b-->
|
||
## 项目相关
|
||
|
||
- 2023-07-10 发布视频[《404星链计划-afrog：快速稳定的漏洞扫描工具》](https://www.bilibili.com/video/BV1Pz4y177PU/)
|
||
|
||
## 最近更新
|
||
|
||
#### [v3.5.6] - 2026-07-19
|
||
|
||
**修复**: OOB 类型漏洞在“最终结果收敛后”丢失请求/响应过程数据，导致 HTML 报告和 -web 页面无法展示完整漏洞过程的问题。
|
||
**-validate**: 现在会先完成全量校验并输出通过项，最后再以汇总列表集中展示所有校验失败的 PoC，方便快速定位问题文件。
|
||
|
||
|
||
#### [v3.5.3] - 2026-05-19
|
||
|
||
**慢任务治理（重要）**
|
||
**新命令 -pedm（推荐体验）**
|
||
**终端体验优化**
|
||
**OOB 检测重构**
|
||
|
||
|
||
#### [v3.3.9] - 2026-02-25
|
||
|
||
**OOB核心升级**
|
||
- 更简洁的 PoC 语法
|
||
- 更稳健的底层逻辑
|
||
- 证据可追溯
|
||
- 老 PoC 一键迁移
|
||
|
||
|
||
#### [v3.2.8] - 2025-12-29
|
||
|
||
**新增**
|
||
- brute 暴力扫描模式
|
||
- 按目标限速（--req-limit-per-target）
|
||
- 实时状态监控（--live-stats）
|
||
** 优化**
|
||
- Go PoC HTTP请求统一化
|
||
- Shiro-key 支持回归
|
||
- Backup-files 支持回归
|
||
|
||
|
||
#### [v3.2.5] - 2025-11-20
|
||
|
||
**修复紧急 bug**
|
||
- 多个协程同时修改共享map数据，导致数据混乱，程序崩溃。
|
||
|
||
|
||
<!--auto_detail_active_end_f9cf7911015e9913b7e691a7a5878527-->
|