Get a prompt and clear overview of your security configuration. Right now!
AECDH (Anonymous Elliptic-curve Diffie-Hellman)
The anonymous Elliptic-curve Diffie-Hellman[431] key exchange[133] is a variant of Elliptic-curve Diffie–Hellman[114][115] key exchange that does not provide authenticity[75][76][77]. Lack of authentication causes that the identity of server cannot be proved, so connection is open for a man-in-the-middle attack[61].
anon
Lack of authentication is combined with anonymous key exchange[397][398], identity of server cannot be proved, so connection is open for a man-in-the-middle attack[61].
Remove the cipher suite from the list of cipher suites supported by your server.
NULL
Encryption algorithm is a null encryption[360][361] that cannot provide confidentiality[91][92][93], so connection is available or disclosed to unauthorized individuals, entities, or processes.
Remove the cipher suite from the list of cipher suites supported by your server.
SHA-1
message authentication code[135][136][137][138] is a hashed message authentication code[139][140][141][142][143][144][145] which is considered secure[462], despite the fact that the underlayingcryptographic hash function[94][95][96][97] (Secure Hash Algorithm 1[202][203][204]) is considered insecure[205][206][207][208][209][210][211].
If your application or requirements specifically call for the use of a message authentication code[135][136][137][138] that does not provide authenticated encryption[74] prefer block cipher mode of operation[82][83][84][85][86] (eg: counter with CBC-MAC[32][33][34], Galois/Counter Mode[46][47][48][49] or message authentication code[135][136][137][138] (eg: Poly1305[458][459]) that proved authenticated encryption over the ones which does not provide it. In case of a hashed message authentication code[139][140][141][142][143][144][145] prefer message authentication code[135][136][137][138] based on Secure Hash Algorithm 2[212][213][214] over the ones based on Secure Hash Algorithm 1[202][203][204].
