Outdated components, unauthenticated API and EOL Electron: what is the security policy?
BeantwortetI went through the diagnostic log of my NAD C 390DD (BluOS 4.18.18, fully up to date) and the desktop Controller app. The findings:
- BusyBox 1.26.2/1.19.4, avahi 0.7/0.6.31 and Perl 5.14.2 in current firmware
- “Not booted secure” in the boot log
- Control API on port 11000, now including an
/mcpendpoint, with no authentication - dropbear SSH running, with no owner access
- BluOS Controller 4.18.0 (macOS) on Electron 42.4.0, which has been end of support since October 2026
Every one of these is a known weak point. Combined, they are worse: outdated software, an open interface and no way for the owner to check anything. “Users have no business on the device” only works if the manufacturer takes over that responsibility in full and visibly. I see no sign of that.
This fits a pattern. Native ARM/Apple Silicon support for the Controller app came only at the last possible moment. Platform and security updates seem to happen when they can no longer be avoided, not when they are due.
Why has NAD still not learned how to treat their "digital" products ? I have no login access I cannot do it. I understand NAD ambition to make the product merely service free but behind the curtain an active update policy is need with digital products. And with AI we have also new security threads.
What I would expect:
- A published support period for security updates per device
- Regular updates of the base components, not just new features
- Authentication, or at least an off switch, for the network API
- A supported Electron version in the Controller app, updated on Electron’s release cycle
- A security contact and public advisories
- Simple possibilities like switch off WLAN
Has anyone received a concrete answer from NAD/Bluesound on this?
-
Offizieller Kommentar
Thanks for taking the time to put this together. Security is something we take seriously across BluOS players and apps, and feedback like this is passed on to our product and engineering teams.
On the BluOS Controller for desktop: we update Electron with our major releases, balancing staying current with the stability and long-term support our customers expect from the app. The next major release moves to a current, supported Electron version.
We don't publish details of our internal security processes, but we do review the components we ship on an ongoing basis and include security updates in our regular BluOS releases.
Post ist für Kommentare geschlossen.
Kommentare
1 Kommentar