CVE-2005-2471: pstopnm in netpbm does not properly use the "-dSAFER" option when calling Ghostscript to convert a PostScri...

Security readout for executives and security teams

This is an old netpbm pstopnm issue where converting a malicious PostScript file could run commands on the processing system. The attacker needs someone or some workflow to process the file, so urgency depends on whether untrusted PostScript is accepted or converted. Exposure is most plausible on legacy or unpatched systems that include netpbm pstopnm and process externally supplied PostScript files, including upload pipelines, mail/document converters, or batch image conversion jobs. Prioritize remediation where file conversion touches external content or business workflows. For systems without PostScript processing, urgency is lower but inventory should still confirm absence of exposure. Mitigation focus: Check distribution advisories for fixed netpbm packages.; Apply vendor updates from Debian, Red Hat, SUSE, or Trustix where applicable.; Restrict pstopnm processing of untrusted PostScript until patched..

Prepared

Jun 29, 2026, 18:40 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.