Is Roon vulnerable to the Log4J security issue? I did a search and haven’t found a topic so hope it’s being looked at to see if there is a risk.
What about Qobuz or Tidal if we use those services?
I’m currently checking my NAS software and shutting off Plex which I use for remote playback until I know it’s safe so I can be sure my music setup is secure.
Absolutely. This said, as long as Roon isn’t remote-accessible, wouldn’t one be correct in assuming it doesn’t expose a service, and thus Log4J isn’t a potential issue (contrary to, say, Plex) ?
This vulnerability impacts Java/JVM-based applications that use log4j.
The Roon applications do not use Java, other than a minimal use of Java required to integrate with the Android platform, but we do not use log4j on Android.
Our cloud services not java-based, and thus not impacted.
I can’t speak for Qobuz or TIDAL, and do not have detailed information about their internal architecture or techs stack–if you are concerned about them, I’d advise contacting them directly.
Doesn’t Roon use ElasticSearch for it’s hosted search index? Although I’m guessing you’re already running ES6 or 7.
btw. I hope this doesn’t come across as as a snarky “I think you’ve missed one…look at me for spotting it”. It was just that I reading this thread after patching one of our older Elastic clusters at the weekend and then thought “But doesn’t Roon also use Elastic as well?”.
My answer yesterday focused on our in-house services and not external or third-party stuff, but we did audit everything. Our Elastic installs are up to date and were not susceptible to this issue.