vulnerability cipher suites on Polycom IP Phones SoundStation Duo

[Anonymous]

hi,

I have an issue with DES cipher vulnerability. I tried to update the config following this kb cipher suites kb . but could not resolve the issue. my IP Phone doesn't have an option to select the minimum TLS version and this vulnerability affected my 8pcs Polycom SoundStation Duo. also I tried to update the firmware to 4.1.1.0934 it has no effect.

the question: how to fix this Vulnerabilities?

this is my cipher suites configuration:

ALL:!DH:!LOW:!EXP:!MD5:!DES:@STRENGTH

Phone Information
Phone Model	SoundStation Duo
Part Number	3111-19000-001 Rev:F
MAC Address	00:04:F2:F4:13:B0
UC Software Version	4.0.7.4180
BootROM Software Version	5.0.7.1284

test result after updated the config:

Starting Nmap 6.40 ( http://nmap.org ) at 2021-12-03 14:48 +08
Nmap scan report for X.X.X.X
Host is up (0.0036s latency).
Not shown: 997 closed ports
PORT     STATE SERVICE
80/tcp   open  http
443/tcp  open  https
| ssl-enum-ciphers:
|   SSLv3:
|     ciphers:
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA - strong
|       TLS_RSA_WITH_AES_128_CBC_SHA - strong
|       TLS_RSA_WITH_AES_256_CBC_SHA - strong
|       TLS_RSA_WITH_DES_CBC_SHA - weak
|       TLS_RSA_WITH_RC4_128_MD5 - strong
|       TLS_RSA_WITH_RC4_128_SHA - strong
|     compressors:
|       NULL
|   TLSv1.0:
|     ciphers:
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA - strong
|       TLS_RSA_WITH_AES_128_CBC_SHA - strong
|       TLS_RSA_WITH_AES_256_CBC_SHA - strong
|       TLS_RSA_WITH_DES_CBC_SHA - weak
|       TLS_RSA_WITH_RC4_128_MD5 - strong
|       TLS_RSA_WITH_RC4_128_SHA - strong
|     compressors:
|       NULL
|_  least strength: weak
5060/tcp open  sip

thanks in advance

regards,

bc

[SteffenBaierUK · Accepted solution]

Hello @imbc00 ,

Welcome to the Poly Community.

If you are not using Microsoft Lync or Skype for Business on-premise UC Software 4.1.1 is not a supported software for your device.

The device, if used in openSIP has the latest Software 4.0.15

Please upgrade to this build and follow the quoted Knova article on how to add the configuration and if this still fails please provide us with a backup of the configuration.

The above is all outlined in the FAQ

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

[Anonymous]

hi,

thanks for your advice, after updating the firmware to 4.0.15 and updating the config as per the KB ,now it's resolved the issue.

thank you

regards,

BC