You have not knowingly seen an exploit in the wild. Competent attackers can be right inside your OS, and many other devices containg within the same network as a result, without you knowing it; persistenly so if they want to.
This is a total failure by the vendors of these freezers.
If you charge money for something that is critical national infrastructure - and the food delivery pipeline is absolutely CNI - and you connect it to the Internet, you should also be responsible for keeping it secure - or at the very minimum at least trying to do so.
The same goes for other CNI such as telecoms (including home routers and phones), broadcasting (including "smart" TVs at the eyeball end), banking and payment processing infrastructure, cloud computing, electricity, gas and water supply, traffic signalling... all modern economies are now almost totally dependent on so many different interlocking internet-connected systems. I've got a stash of food and water at home, a battery powered radio, candles, blankets to keep warm and so on, but that's only really enough to deal with a short-term emergency, not the collapse of technological civilization.
Failure to understand this is not an excuse. Sadly, the only way to deal with this is legislation.
It's one of the major selling points of Linux that Linux admins can do this even if their OS vendor won't, but the whole point of having a distro is to stop you from needing to roll your own solutions, or to have to maintain constant vigiliance to be even remotely secure.
At this point, just the failure to patch this single vulnerability is enough to make me write Ubuntu off as a viable distribution. Volunteer-run distros can fix this, why not a well-resourced company? It's not as if they haven't had the time to fix it, or that porting the fix to their current kernels would be particularly difficult.
This is the final nail in the coffin. I already order my new vservers with debian. I'll keep the existing ones on ubuntu for now, but will not consider ubuntu for anything server side in the future. My reasoning was "Debian is volunteers, they probably won't release fixes as fast as a commercial entity" - obviously the reasoning is backwards.
But I also must say, I am not giving a single dollar to ubuntu nor did I ever do so, so it is also perfectly valid for Ubuntu to not give a damn about me.
Centralized monitoring, so you can check if the local staff are doing their job properly, and in an ideal world, detecting performance degradation so you can schedule maintenance before they break.
Sounds legit, thanks!
I am wondering then what is a good solution for this kind of issues? A physical switch on the freezer that enables/disables remote control over remote monitoring? However the operators will leave this switch on for convenience.
The reason why this very very silly article can continue to exist is that Reliable Sources have deemed this to be notable by repeatedly writing about its subject. If you want to complain about it, you should complain to them.
Wikipedia is a mirror of the world, not an authority that defines it.
Your greedy ISP won't provide you with IPv6 for financial reasons - it's cheaper not to change or upgrade systems. This won't change until they start to provide you with IPv6 for financial reasons, as they reach the point where going to IPv6 starts to be a cost saving for them rather than having to run two different networks at once, with a whole bunch of CGNAT to keep the IPv4 part of it going.