In this article, we show how we reached Ghostscript through most of the applications we tested, exploited a memory corruption bug in its font loader, and bypassed its -dSAFER sandbox to achieve remote command execution across widely used software. On 25 September, we posted a short announcement naming some of the applications and services our research had reached.
The list came from following file-processing dependencies across products that otherwise had little in common. That gave us two connected questions to investigate: which interpreters could we reach through ordinary application features, and could those interpreters safely process the files we sent? We continued into Ghostscript's internals and found several independent bugs of varying impact.






