This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
https://techcrunch.com/2017/12/27/certain-sonos-and-bose-models-can-be-accessed-by-hackers-to-play-sound-remotely/ What is Sonos doing to address a security concern in their products?
More like "Stupid users who open up security vulnerabilities in their networks leave themselves wide open to hackers." In other words, water is wet, sky is blue, and tech magazines (TrendMicro, the originator of the story) purposefully disable security that is the default on 99.999% of the networks out there in order to manufacture click bait stories.
Nothing to see here, unless you make it a habit to enable outside access to your internet connected devices. In which case, you have far more at stake than spooky noises over your Sonos speakers.
According to the release notes on the iOS app store for 8.2.2 (which I can't find on this website), it says:
What's New: Version 8.2.2
This update delivers a couple of performance improvements, bug fixes and a security update for the WiFi WPA2 KRACK vulnerability.
According to the release notes on the iOS app store for 8.2.2 (which I can't find on this website), it says:
What's New: Version 8.2.2
This update delivers a couple of performance improvements, bug fixes and a security update for the WiFi WPA2 KRACK vulnerability.
Yup. It was also due to the fact users were setting their system up with public IP addresses and making them fully accessible to the outside. This was against all recommendations from Sonos.
Well, the article that the OP referenced stated: Sonos has also issued a patch to help plug the hole. We’re still awaiting an official response from Bose.' as did the Engadget article I referenced. I made the assumption it was part of the same release that included the KRACK fix.
Well, the article that the OP referenced stated: Sonos has also issued a patch to help plug the hole. We’re still awaiting an official response from Bose.' as did the Engadget article I referenced. I made the assumption it was part of the same release that included the KRACK fix.
Not sure about that. It may just be the author got the KRACK threat and this one mixed up. Now that I read it, it looks to be the case because a Sonos rep today stated that this is only possible when the user allows public access, which is not recommended.
Edit: I see now that Sonos supposedly put out a patch that limits the data that can be accessed through this hack. That may mean shutting off the port 1400:/status stuff. Maybe someone from Sonos can elaborate.
Yea, not sure about the "misconfigured" network statement. But generally speaking, Sonos responds to the few issues that have been raised. Perhaps not as quickly as we want, but they do. And I wanted to address the sense of "OMG, Sonos doesn't care" implication in the OP's post.
Yea, not sure about the "misconfigured" network statement. But generally speaking, Sonos responds to the few issues that have been raised. Perhaps not as quickly as we want, but they do. And I wanted to address the sense of "OMG, Sonos doesn't care" implication in the OP's post.
Meh. Nobody ever started out a rant with "Sonos cares! But I'm going to have a tantrum anyway!" It's as ubiquitous as "I'm going to dump this in the trash and buy Bose!" and about as accurate.
But I do hate the automatic jumping to a conclusion that isn't supported by the evidence provided. But I'm not a fan of tantrums, either. I gave them up at about age 7. Which was a damn long time ago 🙂
The local network can be penetrated by other vectors. It's important that IoT devices have solid security. If a IoT fridge has a vulnerability and runs a botnet, blaming the user is rich.
I am disappointed to see that the forums continue to be patrolled by ignorant trolls that believe that Sonos doesn't have a duty of care to ensure their devices are free of exploits.