Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 165354

Summary:	CAN-2005-2471 netpbm should use the -dSAFER option when calling Ghostscript
Product:	Red Hat Enterprise Linux 4	Reporter:	Josh Bressers <bressers>
Component:	netpbm	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	Ben Levenson <benl>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.0	CC:	pknirsch
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	impact=low,public=20050724,reported=20050725,source=debian
Fixed In Version:	RHSA-2005-743	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-08-22 13:55:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josh Bressers 2005-08-08 14:22:41 UTC

pstopnm in netpbm does not properly use the "-dSAFER" option when calling
Ghostscript to convert convert a PostScript file into a (1) PBM, (2) PGM, or (3)
PNM file, which allows external user-complicit attackers to execute arbitrary
commands.

The Debian bug report has more information:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319757

Comment 1 Josh Bressers 2005-08-08 14:24:33 UTC

This issue should also affect RHEL2.1 and RHEL3

Comment 2 Josh Bressers 2005-08-08 14:39:43 UTC

twaugh says we should probably use the -dPARANOIDSAFER to also protect against
unwanted reads.

Comment 3 Jindrich Novy 2005-08-10 13:18:15 UTC

Yes, this also affects RHEL2.1 and RHEL3.

I've done a patch that applies to netpbm-9.24 we have in 2.1 and 3.

Comment 5 Red Hat Bugzilla 2005-08-22 13:55:11 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-743.html