I have just put up Majordomo successfully but before I release it out
to our users I want to find a fix to this problem that came in off this
cert, concerning majordomo checking for any unauthorized synlinks... :...
--------- Forwarded message ----------
Date: Thu, 26 Mar 1998 15:03:28 -0600
From: Karl G - NOC Admin <firstname.lastname@example.org>
Subject: Majordomo /tmp exploit
Majordomo allows appending to any file owned by the majordomo user/group.
create a symlink in /tmp to any majordomo file
ex: ln -s /usr/lib/majordomo/majordomo /tmp/majordomo.debug
send a message with any emailer to majordomo with a "/" in the return
address. (i tested with Winbloze Internet Mail)
the owner of majordomo will receive the below message... from then on,
majordomo will be inoperable. (if the above symlink is used) Majordomo
keeps a debug log and appends to it every time it crashes with out
checking ownerships of the symlinks.. or for that matter for symlinks at
Subject: MAJORDOMO ABORT (mj_majordomo)
MAJORDOMO ABORT (mj_majordomo)!!
HOSTILE ADDRESS (no x400 c=) email@example.com
should the wrapper not check for such things?