Actions10
VPN → Submit
AI-generatedOverview
This node integrates with the Vulbox platform to submit vulnerability reports related to VPN resources. It is designed for security researchers, penetration testers, or organizations who want to report discovered VPN vulnerabilities systematically. The node automates the submission of detailed bug reports including metadata such as task association, business information, vulnerability classification, and reproduction steps.
Typical use cases include:
- Automating vulnerability disclosure workflows by submitting VPN-related bugs directly from n8n.
- Integrating vulnerability management processes with other tools via Vulbox API.
- Streamlining reporting with structured data fields to ensure completeness and consistency.
Example: A security team finds a VPN flaw during an audit and uses this node to submit the bug report with all relevant details (title, category, severity, reproduction steps, fix plan) to Vulbox for tracking and vendor notification.
Properties
| Name | Meaning |
|---|---|
| 项目 Task | Select the associated task from a list of tasks. This links the vulnerability report to a specific project or engagement. |
| 漏洞标题 Bug Title | The title or short description of the vulnerability being reported. |
| 漏洞类别 Bug Category | Type of vulnerability: "事件型漏洞" (Event-type vulnerability) or "通用型漏洞" (General vulnerability). |
| 参与评定 Vulnerability Star | Indicates if the vulnerability is a normal one ("普通漏洞") or a starred/selected vulnerability ("星选漏洞"). |
| 厂商名称 Business Name | Select or specify the affected business/vendor name. Can be chosen from a list or entered manually. |
| 厂商域名 Domain | The domain URL of the affected business/vendor, defaulting to the selected business's URL. |
| 一级漏洞类型 Top Level Bug Type Name or ID | Top-level category of the vulnerability, selectable from a dynamic list. |
| 二级漏洞类型 Bug Type Name or ID | Sub-category of the vulnerability, dependent on the top-level type. Hidden for some top-level types like "智能硬件" (Smart Hardware) or "其他" (Others). |
| 漏洞等级 Bug Level | Severity level of the vulnerability: Low (低危), Medium (中危), High (高危), or Critical (严重). |
| 漏洞简述 Bug Paper | A brief summary or abstract describing the vulnerability. |
| 厂商截图 Bug Star Description | Detailed description for starred vulnerabilities, supporting rich HTML content. Only shown if the vulnerability is marked as starred. |
| 漏洞URL Bug URL | URL related to the vulnerability, applicable only for web vulnerabilities. |
| 漏洞参数 Bug Parameter | Parameters involved in the vulnerability, applicable only for web vulnerabilities. |
| 设备 Bug Equipment | Device information related to the vulnerability, applicable only for mobile client vulnerabilities. |
| 平台 Bug Platform | Platform information related to the vulnerability, applicable only for mobile client vulnerabilities. |
| 版本 Bug Version | Version information related to the vulnerability, applicable only for mobile client vulnerabilities. |
| 漏洞POC Bug POC | Proof of Concept code or description demonstrating the vulnerability. |
| 复现步骤 Repetition Step | Required detailed steps to reproduce the vulnerability, supports rich HTML content. |
| 修复建议 Fix Plan | Required recommended fix or mitigation plan, supports rich HTML content. |
| 地区 Area Name or ID | Geographic area related to the vulnerability, selectable from a dynamic list. |
| 行业 Industry Name or ID | Industry sector related to the vulnerability, selectable from a dynamic list. |
| Industry Category Name or ID | Industry category related to the vulnerability, selectable from a dynamic list. |
| 是否匿名 Bug Anonymous | Boolean flag indicating whether the bug report should be submitted anonymously. |
Output
The node outputs JSON data representing the response from the Vulbox API after submitting the vulnerability report. This typically includes confirmation details such as the created bug ID, status, and any messages returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Vulbox API credential configured in n8n to authenticate requests.
- Depends on Vulbox API endpoints for listing tasks, businesses, bug types, areas, industries, and submitting bug reports.
- Dynamic option loading methods are used to populate dropdowns for bug types, areas, industries, etc., requiring network access to Vulbox services.
Troubleshooting
- Missing required fields: The node requires several mandatory fields (e.g., task, bug title, bug category, bug star, business, bug type, bug level, repetition step, fix plan, area, industry, industry category). Omitting these will likely cause API errors.
- Invalid JSON parsing: The business property expects a JSON string that is parsed internally. Malformed input here can cause failures.
- API authentication errors: Ensure the Vulbox API credential is correctly set up and has valid permissions.
- Dynamic options not loading: If dropdown lists fail to populate, check network connectivity and API availability.
- Incorrect field dependencies: Some fields appear conditionally based on others (e.g., bug_url only for Web vulnerabilities). Providing inconsistent data may cause validation issues.
Links and References
- Vulbox API Documentation (example placeholder, replace with actual)
- n8n Expressions Documentation
- n8n Node Development Guide