Actions10
Submit
AI-generatedOverview
This node integrates with the Vulbox platform to manage and submit vulnerability reports related to security tasks. Specifically, the Submit operation allows users to create detailed bug/vulnerability submissions associated with a particular task and business entity.
Typical use cases include:
- Security researchers or teams submitting newly discovered vulnerabilities to a tracking system.
- Automating the reporting process of bugs found during penetration testing or security audits.
- Organizing vulnerability data with rich metadata such as severity, category, affected business, and reproduction steps.
For example, a user can select a specific security task, provide details about a web vulnerability including its URL and parameters, describe reproduction steps and fix plans, and then submit this information directly to Vulbox for further processing.
Properties
| Name | Meaning |
|---|---|
| 项目 Task (task) | The security task to which the bug report is linked. Selected from a searchable list of existing tasks. |
| 漏洞标题 Bug Title | The title or short description of the vulnerability being reported. |
| 漏洞类别 Bug Category | The category of the bug: either "事件型漏洞" (Event-type vulnerability) or "通用型漏洞" (General vulnerability). |
| 参与评定 Vulnerability Star (bug_star) | Indicates if the bug is a normal vulnerability ("普通漏洞") or a starred/featured vulnerability ("星选漏洞"). |
| 厂商名称 Business Name | The vendor or business entity affected by the vulnerability. Can be selected from a list or specified manually. |
| 厂商域名 Domain | The domain name of the business/vendor, defaulting to the URL parsed from the selected business. |
| 一级漏洞类型 Top Level Bug Type Name or ID (bug_type_top) | The top-level classification of the bug type, selectable from a dynamically loaded list. |
| 二级漏洞类型 Bug Type Name or ID (bug_type) | The secondary classification of the bug type, also selectable from a dynamic list. Hidden for certain top-level types like "智能硬件" (Smart Hardware) or "其他" (Others). |
| 漏洞等级 Bug Level | Severity level of the bug: Low (低危), Medium (中危), High (高危), or Critical (严重). |
| 漏洞简述 Bug Paper | A brief textual summary describing the vulnerability. |
| 厂商截图 Bug Star Description (bug_star_desc) | An HTML-formatted description shown only if the bug is marked as starred. |
| 漏洞URL Bug URL | The URL related to the vulnerability, shown only for Web vulnerabilities. |
| 漏洞参数 Bug Parameter | Parameters involved in the vulnerability, shown only for Web vulnerabilities. |
| 设备 Bug Equipment | Device information relevant to the bug, shown only for mobile client vulnerabilities. |
| 平台 Bug Platform | Platform information relevant to the bug, shown only for mobile client vulnerabilities. |
| 版本 Bug Version | Version information relevant to the bug, shown only for mobile client vulnerabilities. |
| 漏洞POC Bug POC | Proof of Concept code or description demonstrating the vulnerability. |
| 复现步骤 Repetition Step | Detailed reproduction steps for the vulnerability, required and supports HTML formatting. |
| 修复建议 Fix Plan | Suggested fix or remediation plan for the vulnerability, required and supports HTML formatting. |
| 地区 Area Name or ID | Geographic area related to the bug, selectable from a dynamically loaded list. |
| 行业 Industry Name or ID | Industry sector related to the bug, selectable from a dynamically loaded list. |
| Industry Category Name or ID (industry_category) | Industry category related to the bug, selectable from a dynamically loaded list. |
| 是否匿名 Bug Anonymous (bug_display) | Boolean flag indicating whether the bug report should be submitted anonymously. |
Output
The node outputs an array of JSON objects representing the response from the Vulbox API after submitting the bug report. Each output item corresponds to one submission and includes metadata constructed by n8n for execution context.
The exact structure of the returned JSON depends on the Vulbox API's response but typically contains confirmation details of the submitted bug, such as IDs, status, and any messages.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Vulbox API service.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- Dynamic option loading for properties like tasks, businesses, bug types, areas, industries, and industry categories relies on Vulbox API endpoints.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Required fields not provided (e.g., task, bug title, reproduction steps, fix plan) will result in validation errors.
- Incorrectly formatted JSON in the business property may cause parsing errors.
- Selecting incompatible bug type combinations might lead to unexpected behavior or API rejection.
Error messages:
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Validation errors: Ensure all required fields are filled and follow expected formats.
- Network or timeout errors: Check network connectivity and Vulbox API availability.