Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 147342 - CAN-2005-0202 mailman flaw
CAN-2005-0202 mailman flaw
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mailman (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Dennis
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-02-07 10:08 EST by Mark J. Cox
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-10 10:05:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:136 high SHIPPED_LIVE Important: mailman security update 2005-02-10 00:00:00 EST

  None (edit)
Description Mark J. Cox 2005-02-07 10:08:35 EST
A flaw in the true_path function of Mailman was discovered. A remote attacker
could make use of this flaw with a carefully crafted URL and gain access to
files such a configuration files or list archives that should otherwise be

Administrators can see if attempts to use this flaw has been made by exmaining
their web server access logs for requests containing ".....///"

Affects: RHEL2.1
Affects: RHEL3
Comment 1 Mark J. Cox 2005-02-08 10:26:49 EST
Note that Apache 2.0 strips multiple slash characters in the
PATH_INFO; therefore this issue is not exploitable when Mailman is
used on an Apache 2.0 server.
Comment 2 Mark J. Cox 2005-02-09 13:33:39 EST
Now public,removing emarbgo
packages in QA
Comment 3 Josh Bressers 2005-02-10 10:05:22 EST
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.


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