Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] The output file name is too long. #5769

Open
1 task done
wa0er opened this issue Oct 25, 2024 · 0 comments
Open
1 task done

[BUG] The output file name is too long. #5769

wa0er opened this issue Oct 25, 2024 · 0 comments
Assignees
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@wa0er
Copy link

wa0er commented Oct 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

Current Behavior

nuclei.exe -l nuclei-test.txt -me output_nuclei-test.md -ts -stats -si 10 -es info

When I execute the command above, if it hits certain templates with longer payloads (such as xss-fuzz, CVE-2019-2767, CVE-2020-7796, CVE-2021-33544, etc.), the output Markdown file name will be particularly long.
In the Windows system, this can lead to some bugs, such as being unable to rename this file or move it to another directory. As a result, deleting this file requires deleting the entire directory it is in. If there are many useful files in that directory, I first need to move those useful files to another directory before deleting the entire directory where this file is located.
Additionally, in another Windows VPS of mine(Windowns 10), there is a situation where the cmd terminal indicates that this template was hit, but no corresponding Markdown file is generated in the physical folder.

Image
Image

Expected Behavior

I suggest adding a flag for nuclei to change the output Markdown file name from 'template name + Full URL' to 'template name + target URLs/hosts specified by the -u or -l parameters.'
This way, the issue of overly long file names can be avoided.

Steps To Reproduce

0

Relevant log output

No response

Environment

  • OS: Windows 10 专业工作站版 22H2
  • Nuclei: v3.3.5

Anything else?

No response

@wa0er wa0er added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Oct 25, 2024
@dogancanbakir dogancanbakir self-assigned this Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants