infobyte / infobyte/faraday_plugins
Nuclei Scan Import Not Showing Sensitive Fields on Vulnerability Details
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
When importing Nuclei scan results (JSONL), several important fields are not being extracted and displayed in vulnerability details. This impacts users who rely on technology detection and extractor data from Nuclei scans.
Related issue: https://github.com/infobyte/faraday/issues/512
Missing Fields
The following Nuclei JSON fields are not currently parsed:
| Field | Purpose | Priority |
|---|---|---|
matcher-name |
Technology detection (e.g., "cloudflare", "nginx") | High |
matcher-status |
Indicates which matcher triggered | Medium |
extracted-results |
Data captured by extractors | High |
extractor-name |
Which extractor matched | Medium |
curl-command |
Reproduction command for validation | Low |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Nuclei JSONL import parser and the vulnerability-details mapping. Trace how matcher-name, matcher-status, extracted-results, extractor-name, and curl-command are handled, then verify that each appears correctly in imported vulnerability details using representative Nuclei results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100