Added the tunnel variable from the nmap results to be used in CascadingRules. #369
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
NMAP reports the tunnel detected in the service when showing the normal result:
SecureCodeBox makes use of the XML output, this is shown by the
-oXparameter:The NMAP XML results report the service name as
imapand the tunnel asssl.The SecureCodeBox NMAP parser does read this tunnel value
secureCodeBox/scanners/nmap/parser/parser.js
Line 279 in 1f26c9f
However this value is later ignored in the portFindings variable
secureCodeBox/scanners/nmap/parser/parser.js
Lines 13 to 61 in 1f26c9f
As a result this tunnel value was unable to be used for CascadingRules. This is fixed by this update and as an example the CascadingRules used for SSLYZE have been updated.
Checklist
npm testruns for the whole project.