News for hackers. Stuff that matters.
Re:50 CVEs in 50 Days: Fuzzing Adobe Reader by danieldk on Thursday December 13, 2018 @04:43AM (#18671086)
Which gives (except for pdf.js) more PDF readers written in C, some with a long history of CVEs, and typically not sandboxed by default.

Since many people are using a PDF reader to read PDFs from relatively untrusted sources, do yourself a favor and at least use a reader that does not have full system access.

macOS: Preview.app (uses macOS sandboxing)

Linux: Evince Flatpak on Wayland (Flatpak uses sandboxing. Wayland because X11 apps can read all keystrokes, mouse events, do screengrabs.)

Windows: no clue

All platforms: in-browser PDF reader with a browser that sandboxes.

Re:50 CVEs in 50 Days: Fuzzing Adobe Reader by rvp-x on Thursday December 13, 2018 @04:54AM (#18671132)
If you're counting on wayland to sandbox arbitrary code execution, you're getting in trouble.
Re:50 CVEs in 50 Days: Fuzzing Adobe Reader by Spivak on Thursday December 13, 2018 @12:30PM (#18674142)
Applications that can send commands to X.org servers can completely control it. The same isn't true for Wayland.

Flatpak is providing the actual application sandboxing, but being allowed to talk to the X server is a huge amount of privilege that can't really be restricted.

Re:50 CVEs in 50 Days: Fuzzing Adobe Reader by danielhlockard on Thursday December 13, 2018 @12:29PM (#18674139)
I think they're counting on flatpak.
Re:50 CVEs in 50 Days: Fuzzing Adobe Reader by Santosh83 on Thursday December 13, 2018 @05:24AM (#18671242)
> Windows: no clue

I think UWP apps are sandboxed by default, so something like Xodo PDF could be a possibility.

Re:50 CVEs in 50 Days: Fuzzing Adobe Reader by Already__Taken on Thursday December 13, 2018 @08:23AM (#18672098)
or Edge