21
Arbitrary code execution breaking sandboxes in KDE Plasma | Kimiblock's Blog (blog.kimiblock.top)
submitted 4 months ago by to c/linux@lemmy.ml
5 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 4 months ago* (2 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 4 months ago (1 child)

    Plasma widgets are a gaping security hole.

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •