News for hackers. Stuff that matters.
Re:Today, we hacked what we'd set out to hack: the iPhone by aemoron on Friday October 23, 2026 @01:08PM (#50212216)
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.

Re:Today, we hacked what we'd set out to hack: the iPhone by motoboi on Friday October 23, 2026 @01:15PM (#50212319)
Too huge attack surface. Good candidate for victim trust (who would not open a pdf file on an iPhone?).

So pdf and images are the best vector for iPhones.

Once you escape the parser you have to reach and escape the sandbox and from there reach the kernel.

Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @01:44PM (#50212730)
That's why you need Rust in any image decoder. FFMPEG too.
Re:Today, we hacked what we'd set out to hack: the iPhone by NetMageSCW on Friday October 23, 2026 @02:11PM (#50213135)
Rust is not a magic security wand.
Re:Today, we hacked what we'd set out to hack: the iPhone by gejose on Friday October 23, 2026 @02:35PM (#50213457)
It might not be a magic security wand, but so many critical vulnerabilities in software trace their origins to memory unsafe code and things like "use after free".

"~70% of the vulnerabilities Microsoft assigns a CVE each year continue to be memory safety issues" - Microsoft [1]

"We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android’s C and C++ code." - Google on Android [2]

This is also worth looking: https://www.chromium.org/Home/chromium-security/memory-safet...

References: 1. https://www.microsoft.com/en-us/msrc/blog/2019/07/a-proactiv... 2. https://blog.google/security/rust-in-android-move-fast-fix-t...

Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @02:42PM (#50213560)
If I were Google I'd try to rewrite Chromium in Rust. The FFMPEG folks should try porting the whole codebase to Rust too. They can always keep the legacy versions for legacy computers (my old n270 netbook can barely play 720p@30FPS anyway, and it's too slow to downsize 4k video to 720 or 480p...), so a bigger amd64 machine will always be -reallistically- needed for anything else than <=720p consumption.
Re:Today, we hacked what we'd set out to hack: the iPhone by nkjoep on Friday October 23, 2026 @03:54PM (#50214452)
What folks at Ladybird did this year. Started adopting rust for part if not all their engine.
Re:Today, we hacked what we'd set out to hack: the iPhone by notpushkin on Monday October 26, 2026 @02:43AM (#50239954)
After trying out Swift first!
Re:Today, we hacked what we'd set out to hack: the iPhone by QuantumNomad_ on Saturday October 24, 2026 @06:37AM (#50219941)
> The FFMPEG folks should try porting the whole codebase to Rust too.

They don’t seem convinced that that would be a meaningful use of time for them. (2025)

https://itsfoss.com/news/ffmpeg-swipe-at-rust/

And 6 months ago someone did a little experiment using Claude to rewrite FFmpeg in Rust. It was by the own description by the person that had the AI do it, significantly slower than FFmpeg even when incorporating assembly code from FFmpeg.

https://github.com/sharifhsn/wedeo

Maybe with further advancements it is now possible to get a better result, or soon.

But if you are going to copy their assembly code into the Rust protect how do you definitively prove that no memory unsafe operations are happening in those parts? Seems to me that either the whole thing should be safe Rust, if the point of the rewrite is memory safety.

Re:Today, we hacked what we'd set out to hack: the iPhone by GoblinSlayer on Saturday October 24, 2026 @05:38AM (#50219587)
In case of ms it's often concurrent userland-kernel transitions, and kernel doesn't control how and when they happen. Copilot is busy optimizing windows 11 and can't riir the kernel.
Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @02:38PM (#50213505)
It cuts down most of the crap trying to trash your machine's RAM (virtual memory in the end, but today it's almost as if you didn't have a MMU). It's good enough.

On less powerful machines, dear Mutt+isync+msmtp users like me, please use AERC (written in Go) against these. It's slower, but far more secure than C. Also, SLRN needs a Go rewritten clone (able to point to slrn's caché) like nothing else. Comp.misc and comp.arch still are extremely valuable.

Re:Today, we hacked what we'd set out to hack: the iPhone by mr_toad on Friday October 23, 2026 @04:23PM (#50214807)
No, but it was created to mitigate these sorts of risks.
Re:Today, we hacked what we'd set out to hack: the iPhone by wat10000 on Friday October 23, 2026 @05:14PM (#50215429)
It kind of is, as is any other memory safe language.

You certainly can still write security vulnerabilities that don't involve memory safety violations, and these languages always have unsafe escape hatches that you can use to shoot yourself in the foot. But as long as you don't just sprinkle unsafe on everything, using a safer language is going to make a ton of vulnerabilities just disappear.

Looking at the issues from this past week, safe languages won't stop you from using 4 as your private key, but they would have entirely prevented the PHP vulnerability.

Re:Today, we hacked what we'd set out to hack: the iPhone by genxy on Saturday October 24, 2026 @01:42AM (#50218608)
They didn't enumerate everything you need, nor did they say Rust was a magic security wand. Cast your gas somewhere else.
Re:Today, we hacked what we'd set out to hack: the iPhone by simplesocieties on Saturday October 24, 2026 @04:56AM (#50219387)
"Seatbelts don't solve car crashes so there's no need to wear one!"
Re:Today, we hacked what we'd set out to hack: the iPhone by steve1977 on Friday October 23, 2026 @02:49PM (#50213643)
Apple has been propagating Swift for more than a decade now and at least in theory, it should be on par with Rust in terms of safety I'd say.
Re:Today, we hacked what we'd set out to hack: the iPhone by frizlab on Friday October 23, 2026 @02:55PM (#50213736)
It mostly is. Has pretty much caught up with all of rust actually (while being much more readable).
Re:Today, we hacked what we'd set out to hack: the iPhone by motoboi on Friday October 23, 2026 @04:53PM (#50215171)
They probably link libraries written in C, given the scope of the pdf and image parsing.
Re:Today, we hacked what we'd set out to hack: the iPhone by OptionX on Friday October 23, 2026 @07:50PM (#50216932)
The problem here is that pdf is over bloated with features and without strictly defined standard. Rust can't help you with that, or any language for that matter. It's akin to upgrading the security system on a house on fire.

The best solution would be ditching it completely for a simpler subset of features. But that will never happen.

Re:Today, we hacked what we'd set out to hack: the iPhone by QuantumNomad_ on Saturday October 24, 2026 @06:29AM (#50219894)
> The best solution would be ditching it completely for a simpler subset of features. But that will never happen.

Like the saying goes:

Everyone uses only 20% of the features, but it's a different 20% for different people.

Re:Today, we hacked what we'd set out to hack: the iPhone by mahboi on Friday October 23, 2026 @01:16PM (#50212342)
Well it was TIFF one time
Re:Today, we hacked what we'd set out to hack: the iPhone by sneurlax on Friday October 23, 2026 @11:55PM (#50218232)
TIFFs were used as part of a PSP jailbreak as well iirc
Re:Today, we hacked what we'd set out to hack: the iPhone by bushbaba on Friday October 23, 2026 @01:49PM (#50212798)
Maybe with LLMs a full rewrite that’s more secure could be done
Re:Today, we hacked what we'd set out to hack: the iPhone by ASalazarMX on Friday October 23, 2026 @02:00PM (#50212961)
LLM and full rewrite are a recipe for cooking something that still has flaws but also doesn't work that well. The root cause is that PDF is an old format from a more innocent era. A new document standard that keeps up with the technical and security advances, learns about the lessons PDF taught us, and allows for easy conversion from old PDFs, would be the ideal solution.

Who am I kidding, I think the PDF format will outlive us.

Re:Today, we hacked what we'd set out to hack: the iPhone by jitl on Friday October 23, 2026 @02:29PM (#50213393)
> PDF is an old format from a more innocent era

if apple parsed pdf with (js, swift, rust) none of this would be possible. the problem is memory-unsafe code.

Re:Today, we hacked what we'd set out to hack: the iPhone by Someone on Friday October 23, 2026 @04:26PM (#50214840)
> if apple parsed pdf with (js, swift, rust) none of this would be possible

Interpreters and compilers can have bugs. Bugs can cause memory safety issues.

Re:Today, we hacked what we'd set out to hack: the iPhone by tannertech on Saturday October 24, 2026 @09:05AM (#50220880)
Since when was javascript memory safe
Re:Today, we hacked what we'd set out to hack: the iPhone by rafram on Saturday October 24, 2026 @02:26PM (#50223804)
Since it was created.
Re:Today, we hacked what we'd set out to hack: the iPhone by tannertech on Sunday October 25, 2026 @04:35AM (#50229456)
Why is it we didn't rewrite coreutils in js a decade ago instead of waiting for rust
Re:Today, we hacked what we'd set out to hack: the iPhone by rafram on Sunday October 25, 2026 @02:06PM (#50234273)
Because it’s a high-level interpreted language. Still memory-safe!

Rust is interesting because it’s a low-level language with strong memory safety. That makes it a good fit for projects like coreutils. I’d argue it makes it a bad fit for many other projects that get rewritten in it, though. Not everything actually needs to be in a low-level language with compile-time memory management.

Re:Today, we hacked what we'd set out to hack: the iPhone by dgellow on Friday October 23, 2026 @02:01PM (#50212978)
A full rewrite of what? iOS? I hope you’re kidding
Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @02:44PM (#50213592)
Apple can rewrite the media and PDF libraries in no time in Swift/Rust, they have tons of money to waste.
Re:Today, we hacked what we'd set out to hack: the iPhone by doc_ick on Friday October 23, 2026 @04:06PM (#50214583)
In no time? What are you talking about? It’d take months even with llms for it to be fully polished and tested if they started now.
Re:Today, we hacked what we'd set out to hack: the iPhone by sneurlax on Friday October 23, 2026 @11:56PM (#50218236)
If anybody has the resources to do it, tho, they do

They have the means, they have the motivation

Lately they have fewer and fewer excuses not to

Re:Today, we hacked what we'd set out to hack: the iPhone by rafaelRiv on Saturday October 24, 2026 @09:50AM (#50221206)
That is magic thinking and even religious
Re:Today, we hacked what we'd set out to hack: the iPhone by cpuguy83 on Saturday October 24, 2026 @10:43AM (#50221738)
The reality is Apple has been working on rewriting bits and pieces in Swift.
Re:Today, we hacked what we'd set out to hack: the iPhone by sjtgraham on Saturday October 24, 2026 @05:20AM (#50219512)
That is essentially "in no time" on Apple's release cadence.
Re:Today, we hacked what we'd set out to hack: the iPhone by NetMageSCW on Friday October 23, 2026 @02:10PM (#50213123)
Never mind - that only applied to origins PDF 1.x.
Re:Today, we hacked what we'd set out to hack: the iPhone by midtake on Friday October 23, 2026 @06:31PM (#50216269)
Does Lockdown block all PDFs?
Re:Today, we hacked what we'd set out to hack: the iPhone by creata on Friday October 23, 2026 @07:21PM (#50216707)
No, it doesn't.
Re:Today, we hacked what we'd set out to hack: the iPhone by creata on Friday October 23, 2026 @06:33PM (#50216285)
If it wasn't PDF it'd be something else. It's everything after the PDF that's alarming here - how did they break out of the app sandbox?
Re:Today, we hacked what we'd set out to hack: the iPhone by tech234a on Friday October 23, 2026 @06:34PM (#50216295)
I wonder if pdf.js would be more secure since it runs inside a webpage and can benefit from the browser sandboxing. Though I guess iOS has generally managed to keep most of its apps native rather than web app wrappers (as has happened on Windows).
Re:Today, we hacked what we'd set out to hack: the iPhone by dpacmittal on Friday October 23, 2026 @06:42PM (#50216368)
pdf is the new swf
Re:Today, we hacked what we'd set out to hack: the iPhone by static_motion on Saturday October 24, 2026 @06:03AM (#50219729)
Incidentally, both created by Adobe.
Re:Today, we hacked what we'd set out to hack: the iPhone by jsonc on Saturday October 24, 2026 @06:10AM (#50219765)
macromedia has entered the chat.
Re:Today, we hacked what we'd set out to hack: the iPhone by static_motion on Saturday October 24, 2026 @04:53PM (#50225153)
You're totally right, brainfart there.
Re:Today, we hacked what we'd set out to hack: the iPhone by aenis on Saturday October 24, 2026 @12:26PM (#50222782)
Its not just IOS. PDFs cause security problems everywhere where they are collected, and have been - for years.

We are running a service which collects documents from our consumers. We have a content disarm service which is basically a blast-proof container without any access rights, fed a stream of source bytes and outputting clean PDFs. Not a month passes without a burst of attempts at poisoning our systems with malicious PDFs. I don't remember when was the last time that we had attempts driven by malicious jpegs or pngs, just PDFs. Its one of those uber-shit Turing-complete file formats that should die long ago.

Re:Today, we hacked what we'd set out to hack: the iPhone by DANmode on Sunday October 25, 2026 @08:43PM (#50237572)
Certainly isn’t just iOS.