NSE: Add STARTTLS Support to SSLv2.nse #320
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The script sslv2.nse doesn't support STARTTLS. The result is that script misses SSLv2 on certain ports such as SMTP, POP3, etc. These changes add support for STARTTLS. This script has been verified by scanning a host on 443, verifying that the script returns results and then checking the same host on port 25.
Author
|
In addition to helping locate and address services supporting SSLv2, the driving need for the change to to help identify services where SSLv2 could be used to attack other TLS services via CVE-2016-0800. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The script sslv2.nse doesn't support STARTTLS. The result is that script misses SSLv2 on certain ports such as SMTP, POP3, etc. These changes add support for STARTTLS. This script has been verified by scanning a host on 443, verifying that the script returns results and then checking the same host on port 25.