Allwinkt
Re:Arbitrary code execution in QubesOS via copy-to-VM error reporting ...
on Sunday August 30, 2026 @08:09AM (#49497982)
The worst part is that in 2020 they explicitly documented that the remote filename is attacker controlled,but still allowed it to reach system()
This is C security 101: never pass untrusted input through a shell. This should have been caught in the review!
Re:Arbitrary code execution in QubesOS via copy-to-VM error reporting ...
on Sunday August 30, 2026 @08:08AM (#49497970)
The worst part is that in 2020 they explicitly documented that the remote filename is attacker controlled,but still allowed it to reach system()
That is C security 101: never pass untrusted input through a shell. This should have been caught in review!