Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 4221

Summary: Possible root compromises via man/groff.
Product: [Retired] Red Hat Linux Reporter: Jason Costomiris <jcostom>
Component: manAssignee: David Lawrence <dkl>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0Keywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-08-23 15:45:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jason Costomiris 1999-07-27 14:01:55 UTC
The RPMs for groff that come with RH 6.0 apply a patch,
groff-1.11-safer.patch, which removes the unsafe groff
commands.

It is possible that the unsafe commands could find their way
back in should the user decide to rebuild groff and not take
the time to kill the unsafe commands.  This situation can be
avoided by changing the /etc/man.config file.  The TROFF and
NROFF lines should be modified to include the -S flag,
indicating that the "safer" mode of groff should be used for
formatting man pages.

Comment 1 Preston Brown 1999-08-23 15:45:59 UTC
If someone rebuilds groff and introduces a security hole, then they
are putting themselves at risk.  adding the -S field to
/etc/man.config will only move the problem around -- other
applications / uses of groff will still have the hole.  This not truly
lead to better security.

We do not recommend that people rebuild packages unless they are very
sure they understand what they are doing.