Document how to test for well-known vulnerabilities

[tomato42]

There are scripts for testing many of the well known vulnerabilities, but there is no one page that lists which scripts test which vulnerability, which vulnerabilities are still missing reproducer scripts (or have incomplete verification scripts) and which can't be tested.

Create a documentation page with those descriptions, include year in the title.

Vulnerabilities and attacks to cover (at least):

• [ ] BEAST
• [ ] CRIME
• [ ] BREACH
• [ ] Lucky 13
• [ ] various attacks on RC4 from around 2013
• [ ] goto fail
• [ ] Heartbleed
• [ ] CCS Injection
• [ ] Triple Handshake
• [ ] BERserk
• [ ] POODLE
• [ ] POODLE TLS (implementations that didn't check padding or all the padding in TLS)
• [ ] POODLE has friends (CVE-2015-4558, CVE-2015-5517, CVE-2015-5369)
• [ ] SMACK/FREAK/SKIP-TLS
• [ ] Logjam
• [ ] MACE
• [ ] Invalid Curve attacks
• [ ] RSA-CRT
• [ ] Bar Mitzvah
• [ ] DROWN
• [ ] SLOTH
• [ ] ROBOT
• [ ] Nonce-disrespecting peers
• [ ] version intolerance and mis-negotiation (negotiating SSLv3 when TLS 1.2 is offered, but TLS 1.0 when TLS 1.0 is offered)
• [ ] Client Hello size intolerance bugs in F5 and Cisco Ironport
• [ ] lack of checks in Finished message
• [ ] last extension empty intolerance of WebSphere
• [ ] SSLv2 support
• [ ] SSLv3 support
• [ ] insecure ciphersuites support
• [ ] insecure renegotiation support
• [ ] secure renegotiation state

Things to consider for test completeness:

• TLS vs DTLS
• protocol versions
• ciphersuites support
• key type support (RSA vs ECDSA vs DSA vs EdDSA)

Other known issues for OpenSSL, NSS and GnuTLS (though having reproducers for CVEs from other implementations would be good too)

(file separate issues when there are no scripts that reproduce the vulnerability or the scripts are incomplete, add that issue to Vulnerability testers project)

[JegadeeshVontlin]

I would like to work on this issue, is there any time limit? How can I proceed further?

[tomato42]

There is no time limit, just take a vulnerability and document how to test for it. Either create a PR with changes to the readthedocs documentation or create a page in the wiki, directly here in github

[JegadeeshVontlin]

I am unable to install sphinx and coverage 2 , not found via pip3 in ubuntu...

Is there any other possibilities to install and test the scripts to begin documentation

[tomato42]

coverage2 is just coverage installed with pip2 (so on python2), but you don't need it to build docs

no idea why sphinx doesn't work for you... it installed just fine for me with python 3.11.5 in a virtual environment