getmail (SSA:2004-278-01)
Posted on: 10/04/2004 03:47 PM

New getmail packages are available for Slackware 9.1, 10.0 and -current to fix a security issue. If getmail is used as root to deliver to user owned files or directories, it can be made to overwrite system files.

More details about this issue may be found in the Common
Vulnerabilities and Exposures (CVE) database:

Here are the details from the Slackware 10.0 ChangeLog:
patches/packages/getmail-4.2.0-noarch-1.tgz: Upgraded to
getmaii-4.2.0. Earlier versions contained a local security flaw
when used in an insecure fashion (surprise, running something as
root that writes to user-controlled files or directories could
allow the old symlink attack to clobber system files! :-)
From the getmail CHANGELOG:
This vulnerability is not exploitable if the administrator does
not deliver mail to the maildirs/mbox files of untrusted local
users, or if getmail is configured to use an external
unprivileged MDA. This vulnerability is not remotely exploitable.
Most users would not use getmail in such as way as to be vulnerable
to this flaw, but if your site does this package closes the hole.
I'd also recommend not using getmail like this. Either run it as the
user that owns the target mailbox, or deliver through an external MDA.
(* Security fix *)

Where to find the new packages:

Updated package for Slackware 9.1:

Updated package for Slackware 10.0:

Updated package for Slackware -current:

MD5 signatures:

Slackware 9.1 package:
d31d3b88d33488fc55061ea154e31457 getmail-3.2.5-noarch-1.tgz

Slackware 10.0 package:
47b5454e061919f2d2128a16fca3a037 getmail-4.2.0-noarch-1.tgz

Slackware -current package:
65f55bffa3f5fb5158f5f5efb590671a getmail-4.2.0-noarch-1.tgz

Installation instructions:

Upgrade the package as root:
# upgradepkg getmail-4.2.0-noarch-1.tgz


Slackware Linux Security Team

Printed from Linux Compatible (