Bug 158993 - CAN-2005-1751 shtool insecure temporary file creation
CAN-2005-1751 shtool insecure temporary file creation
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: mm (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-05-27 11:17 EDT by Josh Bressers
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-25 18:18:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-05-27 11:17:53 EDT
Race condition in shtool 2.0.1 and earlier allows local users to
create or modify arbitrary files via a symlink attack on the
.shtool.$$ temporary file.

mm contains shtool in its source.
Comment 1 Nalin Dahyabhai 2005-08-25 18:02:50 EDT
shtool is used at build-time, and is not part of either the mm or mm-devel
binary packages.
Comment 2 Josh Bressers 2005-08-25 18:09:48 EDT
Correct, this issue (while very remote I know) is only exploitable if mm is
rebuilt from source.

The advisory states that shtool is only vulnerable if it is used for the
following operations:
tarball, subst, scpp and path.

I have not verified if mm uses these or not.
Comment 3 Nalin Dahyabhai 2005-08-25 18:16:10 EDT
During package build, the makefile calls shtool for these operations:
  version mkdir install
If you attempt to make a new tarball, either with the "snap" or "dist" targets
(we don't), then it's used for:
  fixperm version tarball

So I don't think we have a problem here.
Comment 4 Nalin Dahyabhai 2005-08-25 18:18:45 EDT
Closure note: if we update to a newer version of mm, the problem goes away even
for the make targets we don't call, so marking this WONTFIX.
Comment 5 Nalin Dahyabhai 2005-08-25 18:19:15 EDT
... except I actually marked it DEFERRED.

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