3 ms·
This is the key point; "Nevertheless, the fact that a certain web server supports this anachronistic protocol provides an interesting indicator that other vuln
by bruce511 3y ago
This is the key point;
"Nevertheless, the fact that a certain web server supports this anachronistic protocol provides an interesting indicator that other vulnerabilities and security issues may (and most likely will) be present on the same system."
SSLv2 is, in itself, harmless since no random user using their browser will ever use it.
However the fact it is still switched on implies that the site contains some very old code in the stack. Their server/ OpenSSL, or whatever is old- which likely means the whole stack is old. Since the server likely also supports SSLv3, a well crafted attack could steal the private key.
Of course a site that is this old is also likely to have more-or-less zero (human) traffic, and protects likely zero actual information. So while an easy target, probably not a rich one.
Doing a deeper analysis of these sites would be interesting.
Equally a similar scan for SSLv3 would be good as a comparison statistic. (I expect the number is pretty similar.)
- hannob 3y ago> SSLv2 is, in itself, harmless since no random user using their browser will ever use it. Erh... No. That was actually the main result of the DROWN paper and eventually the reason why everyone was disabling backwards compatibility with SSLv2: https://drownattack.com/ https://drownattack.com/ The mere fact that you are supporting SSLv2 means that an attacker can abuse this to do key operations with your private key.