Knowledge Base

C

Cipher Suite: TLS_­RSA_­WITH_­AES_­128_­CCM

Summary

code:
(0xc0, 0x9c)
IANA Name:
TLS_RSA_WITH_AES_128_CCM

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
A+
Encryption Type
Name
AES-128
Security
Encryption algorithm Advanced Encryption Standard[169][170][171][172][173][174][175][176] is a block cipher[524][525][526][527] for which there is no known practical attack that would allow the attacker to recover the encrypted text without knowledge of the key when the algorithm is implemented correctly. However improper implementations may lead to a side-channel attack[106][107][108] as it has happened in case of OpenSSL[519][520] [161][162][163].
Recommendations
Prefer cipher suites with greater key size of AES (eg: perfer AES-256 over AES-128).
A+
Encryption Mode
Name
Counter with CBC-MAC (CCM)
Security
block cipher mode of operation[293][294][295][296][297] counter with CBC-MAC[266][267][268] is considered secure. It provides provides authenticated encryption[563] which simultaneously assure the confidentiality[198][199][200] and authenticity[201][202][203] of data.
Recommendations
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.
A+
Encryption Key Size
Name
128
Security
The symmetric key[193][194][195] withkey size[438] more than 128 bits as it is should be according to National Institute of Standards and Technology[428][429] so it is not vulnerable to preimage attack[215] and it cannreliably prove that message came from the stated sender (its authenticity) and has not been changed, so connection is not open for a man-in-the-middle attack[414].
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server.
A+
Encryption Block Size
Name
128
Security
The block cipher[524][525][526][527] uses a block size[409] larger than 64 bits, so it is not vulnerable to sweet32 attack[496][497][498][499].
Recommendations