18
Arbitrary code execution breaking sandboxes in KDE Plasma | Kimiblock's Blog
(blog.kimiblock.top)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
KDE has a history of doing that. Plasma widgets are a gaping security hole. You can poke a hole through root. I'm pretty sure you can traverse up the JS object hierarchy from a widget and modify the whole desktop in anyway you want. At least at some point this was possible. A widget can and has deadlocked plasmashell from even loading. Their response was basically "works as intended" and closed the issue.
Aka "thing that isn't sandboxed, never has been sandboxed, and never has been claimed to be sandboxed, is in fact not sandboxed". Just like any app from your distro repositories, or appimages, or games in Steam... Or even most Flatpaks by default for that matter.
Widgets being sandboxed would be cool and is a long term goal (which is way easier said than done!), but don't present them not being sandboxed as some irresponsible thing someone does because they don't care. Your expectations of security simply are simply completely misplaced.
That doesn't matter from a user perspective. You can't expect the layman to know how dangerous a simple widget is.
OMG, did they copy Microsoft's "Active Desktop"? Sounds like this exactly.