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

Suggestion: Add all vulnerabilities from testssl output #3

Open
s3nn opened this issue Jul 10, 2018 · 1 comment
Open

Suggestion: Add all vulnerabilities from testssl output #3

s3nn opened this issue Jul 10, 2018 · 1 comment

Comments

@s3nn
Copy link

s3nn commented Jul 10, 2018

Hey, I was wondering if you are considering adding an option to parse all vulnerabilities from testssl output! I made a few changes to your script for my own personal use, if you want I can (try) and submit a pull request. However, I just wanted to know if there was a specific reason you don't already do this and rely on the hard-coded dictionary.

Thanks, awesome script btw!

@aress31
Copy link
Owner

aress31 commented Jul 10, 2018

Hi @s3nn,

Thanks for your feedback.

Indeed, there is a reason behind my choice of relying on a hard-coded dictionary for the vulnerabilities to parse. This is mainly due to the selection of findings I usually include into my pentest reports (I willingly ignore some testssl findings that I do not judge super relevant for my cases). This is also due, to my need of including the generated Excel tables within the pentest report (.docx) without having to change the page orientation.

In previous versions of the script, I had a -filter option which let the user decide of what vulnerability to parse but it was a bit heavy, therefore I decided that any change would be made by commenting (out) directly the source code.

Maybe this feature could be brought back with default (which would process my current choice of vulnerabilities) and all (which would process all vulnerabilties) values.

Kind regards,
Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants