Red Hat Bugzilla – Bug 132859
cdrecord has a security problem
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
Someone posted an an exploit for cdrecord on Mandrake. I have tried it
on RedHat Enterprise WS 3.0 and it worked here too. After running the
exploit script I had been left with a setuid root shell named /tmp/ss.
Notice that to make this work cdrecord needs to be installed setuid
root. RHEL WS 3.0 does not install cdrecord as setuid root by default.
However, according to cdrecord man page, installing cdrecord with
setuid root permission is recommended way of installing cdrecord to
allow the ordinary users to use it. Although RedHat does not ship it
with setuid root permissions, many system administrators do change it
to setuid root to allow regular users to use it. Therefore it is still
a security bug that needs to be fixed as soon as possible.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Extract the exploit script from
2. run the script
Actual Results: There is a setuid root file named /tmp/ss
Expected Results: /tmp/ss should not have setuid root permissions.
cdrecord on RHEL does not need to be setuid to allow normal users to
use it as the permissions of the writer device get changed by
pam_console_apply at console login. Therefore don't make cdrecord
Dropping security severity.
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.