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.
shtool is used at build-time, and is not part of either the mm or mm-devel
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
tarball, subst, scpp and path.
I have not verified if mm uses these or not.
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.
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.
... except I actually marked it DEFERRED.