Vulbox icon

Vulbox

Interact with Vulbox

Actions10

Task → Submit

AI-generated

Overview

This node integrates with the Vulbox platform to submit detailed vulnerability reports related to specific tasks. It is designed for security researchers, bug bounty hunters, or organizations managing vulnerability disclosures. The node allows users to provide comprehensive information about a discovered bug, including its classification, severity, reproduction steps, and suggested fixes.

Typical use cases include:

  • Submitting new vulnerability reports to a task in Vulbox.
  • Automating the reporting process as part of a security workflow.
  • Ensuring consistent and structured submission of bug details to Vulbox.

For example, a security researcher who has identified a web vulnerability can use this node to submit the bug title, category, severity level, affected business, reproduction steps, and fix plan directly into Vulbox without manual entry on the platform.

Properties

Name Meaning
项目 Task (task) Select the target task from a list to which the vulnerability report will be submitted.
漏洞标题 Bug Title The title or summary name of the vulnerability being reported.
漏洞类别 Bug Category The category of the bug: either "事件型漏洞" (Event-type vulnerability) or "通用型漏洞" (General vulnerability).
参与评定 Vulnerability Star Indicates if the bug is a normal vulnerability or a starred (highlighted) vulnerability. Options: "普通漏洞" (Normal), "星选漏洞" (Starred).
厂商名称 Business Name Select or specify the vendor/business associated with the vulnerability. Can be chosen from a list or entered manually.
厂商域名 Domain The domain URL of the vendor/business, defaulting to the selected business's URL.
一级漏洞类型 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 secondary classification of the vulnerability type, 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), "严重" (Critical).
漏洞简述 Bug Paper A brief description or abstract summarizing the vulnerability.
厂商截图 Bug Star Description Additional description shown when the vulnerability is starred; supports rich HTML content.
漏洞URL Bug URL The URL related to the vulnerability, applicable mainly for web vulnerabilities.
漏洞参数 Bug Parameter Parameters involved in the vulnerability, relevant for web bugs.
设备 Bug Equipment Device information related to the vulnerability, used for mobile client vulnerabilities.
平台 Bug Platform Platform information for mobile client vulnerabilities.
版本 Bug Version Version number or identifier related to the vulnerable software or app.
漏洞POC Bug POC Proof of Concept details demonstrating the vulnerability.
复现步骤 Repetition Step Detailed steps to reproduce the vulnerability; required field supporting rich HTML content.
修复建议 Fix Plan Suggested remediation or fix plan for the vulnerability; required field supporting 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 Specific industry category within the broader industry, selectable from a dynamic list.
是否匿名 Bug Anonymous Boolean flag indicating whether the bug report should be anonymous.

Output

The node outputs a JSON array containing the response data returned by the Vulbox API after submitting the bug report. This typically includes confirmation details such as the created bug ID, status, and any messages from the server.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Vulbox API via an API key credential configured in n8n.
  • The node depends on dynamic option loading methods to populate lists for tasks, businesses, bug types, areas, industries, and categories.
  • Proper network access to the Vulbox service endpoint is necessary.

Troubleshooting

  • Missing Required Fields: Ensure all required properties (e.g., task, bug_title, bug_category, bug_star, business, bug_type_top, bug_type, bug_level, repetition_step, fix_plan, area, industry, industry_category) are provided. Missing these will cause submission errors.
  • Invalid JSON Parsing: The business property expects a JSON string that is parsed internally. If the business value is malformed, it may cause errors.
  • API Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Dynamic Option Loading Failures: If lists for tasks, businesses, or bug types fail to load, check network connectivity and API availability.
  • Field Visibility Issues: Some fields appear conditionally based on other selections (e.g., bug_url only shows for Web vulnerabilities). Make sure to select appropriate values to reveal all needed inputs.

Links and References

Discussion