-
Notifications
You must be signed in to change notification settings - Fork 457
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
Add check for SLOTH vulnerability #126
Comments
Any comments? I'm not sure which type of vulnerability scanners will be accepted and which won't. |
I haven't had time to look into what SLOTH is but my rule for plugins is that I will reject plugins that redo the same thing as existing ones, but provide a different UI/output. |
SLOTH is about MD5 and/or SHA1 hash algorithms being used in signatures. TLS 1.2 adds the new signature_algorithms extension and the client and server can negotiate which hash algorithms are used for signatures. This is separate from the cipher suites. So the information about which signature algorithms the server supports is not already available in the XML or text display. No existing plug-in does this. Clients or servers allowing MD5 in signature_algorithms is a vulnerability, and the SLOTH attack exploits it to break TLS. In addition, some TLS implementations have a related vulnerability where the client or server will accept MD5/SHA1 even when it does not advertise it, which means it can still be exploited. The MD5 attack is cheap enough for anyone to perform. The SHA1 attack is within the reach of intelligence agencies. |
Sounds good - yeah that sounds definitely like a valid, new plugin. This might require some changes to https://github.com/nabla-c0d3/nassl to add some new OpenSSL bindings for the signature_algorithms extension. |
Might be the same as #685 |
How about a plug-in for detecting the SLOTH TLS vulnerability?
https://www.mitls.org/pages/attacks/SLOTH
I might write it, but I'd only want to go to that effort if it would likely be incorporated.
I'm thinking it would report on which algorithms the server says it supports, but also try MD5 and SHA1 anyway even if the server doesn't say it supports them, because a number of libraries have been found to incorrectly accept algorithms they don't advertise.
The text was updated successfully, but these errors were encountered: