News for hackers. Stuff that matters.
Re:Today, we hacked what we'd set out to hack: the iPhone by enjoytheview on Friday October 23, 2026 @01:13PM (#50212286)
PDF has been an entry point since forever, it is extremely complex and can in some cases even run javascript, it has a huge attack surface.
Re:Today, we hacked what we'd set out to hack: the iPhone by xvector on Friday October 23, 2026 @09:09PM (#50217460)
Why can't Apple just sandbox the damn thing? Run the renderer in a VM, call it a day.

Or just spend a few billion tokens rewriting the whole chain in a memory safe language. This nonsense is inexcusable in 2026

Re:Today, we hacked what we'd set out to hack: the iPhone by kccqzy on Friday October 23, 2026 @09:57PM (#50217708)
I sincerely believe you need much more than one billion tokens to rewrite the entire PDF dependency stack in a memory safe language. I think you underestimate how many features PDF has.
Re:Today, we hacked what we'd set out to hack: the iPhone by dd8601fn on Saturday October 24, 2026 @03:02AM (#50218902)
I wish that Apple today was a little more like the Apple that ruthlessly murdered the floppy disc and Flash.
Re:Today, we hacked what we'd set out to hack: the iPhone by 9dev on Saturday October 24, 2026 @06:22AM (#50219853)
Seriously though, I wonder why nobody really attempted to dethrone PDF yet. How hard can it be (famous last words) to design a document format that allows what people generally expect from a PDF, but without the multimedia and interactive parts that are dangerous?
Re:Today, we hacked what we'd set out to hack: the iPhone by hirako2000 on Saturday October 24, 2026 @07:02AM (#50220105)
Network effect. Most documents are PDF. You would need at least backward compatibility, which would mean opening doors to the existing problem.
Re:Today, we hacked what we'd set out to hack: the iPhone by dnpls on Saturday October 24, 2026 @11:40AM (#50222331)
Got it. So if I want to hack anything, check if it can open PDF files first.
Re:Today, we hacked what we'd set out to hack: the iPhone by hirako2000 on Monday October 26, 2026 @03:22AM (#50240252)
You may have even more luck if your input gets injected into a prompt that gets executed by an agent having internet access.

Re security, there are many pdf viewers, so the rewrites exist, and some of them do not have the js execution engine and all that jazz that opens up all sorts of potential exploits.

Re:Today, we hacked what we'd set out to hack: the iPhone by kccqzy on Saturday October 24, 2026 @09:01AM (#50220864)
Because the dangerous parts are not the multimedia and interactive parts. These parts are rarely used. Even if you remove these parts from your PDF reader it’s not a meaningful security improvement. Almost all exploits are in the boring 2D text/graphics/images parts.
Re:Today, we hacked what we'd set out to hack: the iPhone by legulere on Saturday October 24, 2026 @01:06PM (#50223154)
Microsoft tried with (Open)XPS and failed
Re:Today, we hacked what we'd set out to hack: the iPhone by seanieb on Saturday October 24, 2026 @05:05AM (#50219426)
Firefox has been working on this and are making good headway over the last few years.
Re:Today, we hacked what we'd set out to hack: the iPhone by notpushkin on Monday October 26, 2026 @02:32AM (#50239881)
Considering they’ve also made pdf.js, I have hope.
Re:Today, we hacked what we'd set out to hack: the iPhone by sneurlax on Friday October 23, 2026 @11:53PM (#50218227)
The sandbox is just another layer
Re:Today, we hacked what we'd set out to hack: the iPhone by dyzone on Saturday October 24, 2026 @02:07AM (#50218711)
A bulletproof vest is just another layer.
Re:Today, we hacked what we'd set out to hack: the iPhone by sneurlax on Friday November 06, 2026 @11:18AM (#50394347)
yes, and it usually doesn't cover anything except your torso :)
Re:Today, we hacked what we'd set out to hack: the iPhone by iririririr on Saturday October 24, 2026 @01:33AM (#50218575)
it offers just enough cover and deniability. Q.e.d this sub thread.

it's a feature. expect next exploit to also be pdf or image related.

Re:Today, we hacked what we'd set out to hack: the iPhone by ylk on Saturday October 24, 2026 @05:36AM (#50219575)
It's sandboxed, not in a VM but using the *OS sandbox/seatbelt. Running all renderers in a separate VM on a consumer phone sounds like a terrible time when you need to stay competitive regarding performance, responsiveness, etc.
Re:Today, we hacked what we'd set out to hack: the iPhone by throawayonthe on Saturday October 24, 2026 @01:47PM (#50223502)
i mean, we already run all apps in separate VMs...
Re:Today, we hacked what we'd set out to hack: the iPhone by ylk on Saturday October 24, 2026 @09:38PM (#50227394)
On which OS? Android and iOS don’t. Not even Qubes does.
Re:Today, we hacked what we'd set out to hack: the iPhone by aenis on Saturday October 24, 2026 @12:31PM (#50222842)
Two problems.

PDFs may need to be further forwarded or edited on user's machine(s). Doing this in VM might save your device, only to pass the problem further down the road to a more vulnerable system.

The safe thing to do is to disarm the file - convert it in a blast proof VM. The conversion can and probably should be further tuned to explicitly disable some of the crazier, more moronic features of the format, sacrificing compatibility for safety. The same should be done with all other binary formats. It costs next to nothing, considering how crazy OP are today's phones. I wonder why it has not been done yet.

The other problem: I am not 100% sure if a clean rewrite would yield a safe viewer. As others have mentioned, PDFs can contain scripts. You'd always have to run them in VMs.