This is fixed in S2 and will never be fixed in S1.

Choose your poison.

That is really not good enough.

So when Sonos claim on their website, under the S1 app heading “You can continue listening with your Sonos system as you do today. Your system will receive bug fixes and security patches,…....” they are not being truthful.

Unfortunate you feel that way. It’s pretty similar to the way all “smart” device systems work. Windows 3.1 doesn’t get software or security patches on my ‘386 machine, which also can’t run Windows 11. Similarly, my original iPhone doesn’t run iOS13. 

If you set up your Synology properly, as explained in more than one thread, you can continue to use your S1 without issue. 

Perhaps I have missed something here as I am new to this forum.

Could you please direct me to the information which will enable me to set up my system properly and addresses the issue of S1 security vulnerability mentioned in my original post?

Thanks

Typing the word “Synology” or “DSM”  in the search box brings up quite a few threads. I’ll list just a couple of them here, and allow you to do further reading if you desire.

However, if you continue to use S1, as @controlav stated, you’re going to be limited to SMB v1, due to the fact that there’s not room left in the memory to update the Linux kernel required for S1 devices so as to insert the ability to use higher versions of SMB.

The user @Stanley_4 has posted in many threads a solution that he has put on a  website in which he covers how to set up a pi device to act as a more secure gateway. He discusses/links to it in this thread amongst many others:

 In most cases, since the access is internal, and behind a firewall, or should be, the actual exposure for SMB v1 on a Sonos system is relatively limited, but YMMV. 

Many thanks for the very helpful info. I will see how it goes.