Knowledge Base

F

Cipher Suite: TLS_­RSA_­EXPORT_­WITH_­RC2_­CBC_­40_­MD5

Summary

code:
(0x00, 0x06)
IANA Name:
TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5

Check your host!

Type a URL to analyze a service

Get a prompt and clear overview of your security configuration. Right now!

Components

C
Key Exchange Method
Name
Rivest–Shamir–Adleman (RSA)
Security
RSA[320][321] key exchange is a key exchange[467] that has no forward secrecy[135][136][137][138], and does not protect past sessions against future compromises. If long-term secret keys or passwords are compromised, encrypted communications and sessions recorded in the past can be retrieved and decrypted. Throughout its history RSA encryption has had many security flaws[310][311][312][313][314][315] and was affected by variety of attack types: chosen-ciphertext attack[557] (eg: Bleichenbacher's attack[76][77], ROBOT attack[540][541][542][543]), side-channel attack[106][107][108] (eg: padding oracle attack[45][46][47][48], like Bleichenbacher's cat[337][338][339][340]).
Recommendations
Always prefer cipher suites with PFS property over the non-PFS ones. Note that performance considerations implies preferring Ephemeral Elliptic-curve Diffie–Hellman[91][92] over Ephemeral Diffie-Hellman[142][143][144][145].
A+
Authentication Method
Name
Rivest–Shamir–Adleman (RSA)
Security
Rivest–Shamir–Adleman[80][81][82] is a digital signature[231][232][233][234] algorithm, which is considered secure, however there are known weaknesses[322][323][324][325][326].
Recommendations
F
Encryption Type
Name
RC2-40
Security
Encryption algorithm Rivest Cipher 2[49][50] is a block cipher[524][525][526][527] which is theoretically weakened against vulnerabilities[240][241] (eg: related-key attack[53], chosen-plaintext attack[477]), but RC2 as a 40-bit encryption key size[394][395] is weakened against brute-force attack[555]. It cannot provide confidentiality[198][199][200], so connection is available or disclosed to unauthorized individuals, entities, or processes.
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server.
B
Encryption Mode
Name
Cipher Block Chaining (CBC)
Security
Encryption mode is cipher block chaining[132][133][134]. It is vulnerable[103] to timing attack[479] (eg: Lucky Thirteen attack[331][332]) and padding oracle attack[45][46][47][48] (eg: POODLE attack[362][363][364]).
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server or at least set the cipher suite order explicitly and any cipher suite modes be preferred over ciphers suites with CBC modes.
D
Encryption Key Size
Name
40
Security
Any symmetric key[193][194][195] with key size[438] less than 128 bits are disallowed by National Institute of Standards and Technology[428][429] as it is vulnerable to preimage attack[215] in theory. It cannot reliably prove that message came from the stated sender (its authenticity) and has not been changed, so connection is open for a man-in-the-middle attack[414].
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server.
C
Encryption Block Size
Name
64
Security
Any block cipher[524][525][526][527] uses a block size[409] of 64 bits is vulnerable to sweet32 attack[496][497][498][499].
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server, or setup yout server to enforce changing session key regularly (rekeying[567]).
B
Message Authentication Code
Name
MD5
Security
message authentication code[128][129][130][131] is a hashed message authentication code[418][419][420][421][422][423][424] which is considered secure[435][436], despite the fact that the underlaying cryptographic hash function[510][511][512][513] (MD5[227][228][229]) is considered insecure[139][140] as it vulnerable to collision attack[566] in practice and to preimage attack[215] in theory.
Recommendations
Leading client applications do not use this type of message authentication code[128][129][130][131]. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry. If your application or requirements specifically call for the use of a message authentication code[128][129][130][131] that does not provide authenticated encryption[563] prefer block cipher mode of operation[293][294][295][296][297] (eg: counter with CBC-MAC[266][267][268], Galois/Counter Mode[65][66][67][68] or message authentication code[128][129][130][131] (eg: Poly1305[289][290]) that proved authenticated encryption over the ones which does not provide it. In case of a hashed message authentication code[418][419][420][421][422][423][424] prefer message authentication code[128][129][130][131] based on Secure Hash Algorithm 2[71][72][73] over the ones based on MD5[227][228][229].