Actions10
Vulnerability → Submit
AI-generatedOverview
This node integrates with the Vulbox platform to submit vulnerability reports. It is designed for security researchers, bug bounty hunters, or organizations that want to report discovered vulnerabilities in a structured and automated way. By using this node, users can programmatically submit detailed vulnerability information including classification, reproduction steps, fix suggestions, and related metadata.
Practical examples include:
- Automatically submitting newly discovered bugs from a scanning tool into Vulbox.
- Integrating vulnerability reporting into a CI/CD pipeline to track security issues.
- Centralizing vulnerability submissions from multiple sources into Vulbox.
Properties
| Name | Meaning |
|---|---|
| 项目 Task (task) | Select the target project task to which the vulnerability belongs. This is chosen from a list of available tasks. |
| 漏洞标题 Bug Title (bug_title) | The title or short description of the vulnerability being submitted. |
| 漏洞类别 Bug Category (bug_category) | The category of the vulnerability: "事件型漏洞" (Event-type vulnerability) or "通用型漏洞" (General vulnerability). |
| 参与评定 Vulnerability Star (bug_star) | Indicates if the vulnerability is a normal one ("普通漏洞") or a starred/selected vulnerability ("星选漏洞"). |
| 厂商名称 Business Name (business) | The vendor or business associated with the vulnerability. Can be selected from a list or specified manually. |
| 厂商域名 Domain (domain) | The domain URL of the vendor/business, defaulting to the business's URL if available. |
| 一级漏洞类型 Top Level Bug Type Name or ID (bug_type_top) | The top-level classification of the vulnerability type, selectable from a dynamic list. |
| 二级漏洞类型 Bug Type Name or ID (bug_type) | The second-level classification of the vulnerability type, dependent on the top-level type. Hidden for some top-level types like "智能硬件", "其他", "其它". |
| 漏洞等级 Bug Level (bug_level) | The severity level of the vulnerability: Low (低危), Medium (中危), High (高危), or Critical (严重). |
| 漏洞简述 Bug Paper (bug_paper) | A brief summary or abstract describing the vulnerability. |
| 厂商截图 Bug Star Description (bug_star_desc) | Additional description shown only if the vulnerability is starred. Supports HTML editing. |
| 漏洞URL Bug URL (bug_url) | The URL related to the vulnerability, shown only for web vulnerabilities. |
| 漏洞参数 Bug Parameter (bug_parameter) | Parameters involved in the vulnerability, shown only for web vulnerabilities. |
| 设备 Bug Equipment (bug_equipment) | Device information, shown only for mobile client vulnerabilities. |
| 平台 Bug Platform (bug_platform) | Platform information, shown only for mobile client vulnerabilities. |
| 版本 Bug Version (bug_version) | Version information, shown only for mobile client vulnerabilities. |
| 漏洞POC Bug POC (bug_poc) | Proof of Concept details for the vulnerability. |
| 复现步骤 Repetition Step (repetition_step) | Required detailed steps to reproduce the vulnerability. Supports HTML editing. |
| 修复建议 Fix Plan (fix_plan) | Required suggested fix or remediation plan for the vulnerability. Supports HTML editing. |
| 地区 Area Name or ID (area) | Geographic area related to the vulnerability, selectable from a dynamic list. |
| 行业 Industry Name or ID (industry) | Industry classification related to the vulnerability, selectable from a dynamic list. |
| Industry Category Name or ID (industry_category) | Industry category related to the vulnerability, selectable from a dynamic list. |
| 是否匿名 Bug Anonymous (bug_display) | Boolean flag indicating whether the submission should be anonymous. |
Output
The node outputs JSON data representing the response from the Vulbox API after submitting the vulnerability. This typically includes confirmation details such as the created vulnerability 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 for authentication.
- Depends on Vulbox platform services to accept vulnerability submissions.
- Dynamic option loading depends on Vulbox API endpoints for lists such as tasks, businesses, bug types, areas, industries, and industry categories.
Troubleshooting
- Missing required fields: The node requires several mandatory fields such as task, bug title, bug type, bug level, repetition steps, and fix plan. Omitting these will likely cause errors.
- Invalid JSON parsing: The business property expects a JSON string to parse the vendor name and URL. Malformed JSON here may cause failures.
- API authentication errors: Ensure the Vulbox API credentials are correctly set up and have sufficient permissions.
- Dynamic options not loading: If lists like tasks or bug types fail to load, check network connectivity and API availability.
- Incorrect field dependencies: Some fields appear conditionally based on other selections (e.g., bug_type depends on bug_type_top). Selecting incompatible combinations may cause unexpected behavior.
Links and References
- Vulbox Official Website
- n8n Expressions Documentation
- Vulbox API Documentation (if publicly available)