First published: Thu Jun 03 2010(Updated: )
Dan Rosenberg reported that when MBX locking is enabled in exim, local users could exploit a race condition to change permissions of other non-root users' files. This could lead to a denial of service, to create new files owned by other users in unauthorized locations, or to possibly escalate privileges. Further information is available from the upstream bug report [1] and this has been fixed upstream in exim 4.72 [2]. [1] <a href="http://bugs.exim.org/show_bug.cgi?id=989">http://bugs.exim.org/show_bug.cgi?id=989</a> [2] <a href="http://vcs.exim.org/viewvc/exim/exim-src/src/transports/appendfile.c?r1=1.25&r2=1.26">http://vcs.exim.org/viewvc/exim/exim-src/src/transports/appendfile.c?r1=1.25&r2=1.26</a> While exim is built to support the MBX format, it is not the default for local mail delivery (Unix mailbox support is the default). This will only affect users that use the "mbx_format" option in the appendfile transport.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Exim Exim | =4.70 | |
Exim Exim | =4.69 | |
Exim Exim | =4.66 | |
Exim Exim | =4.10 | |
Exim Exim | =4.24 | |
Exim Exim | =4.30 | |
Exim Exim | =4.21 | |
Exim Exim | =4.51 | |
Exim Exim | =4.67 | |
Exim Exim | =4.63 | |
Exim Exim | =4.43 | |
Exim Exim | =4.22 | |
Exim Exim | =4.40 | |
Exim Exim | =4.52 | |
Exim Exim | =4.60 | |
Exim Exim | =4.61 | |
Exim Exim | =4.68 | |
Exim Exim | =4.54 | |
Exim Exim | =4.23 | |
Exim Exim | =4.62 | |
Exim Exim | =4.32 | |
Exim Exim | =4.42 | |
Exim Exim | =4.31 | |
Exim Exim | =4.44 | |
Exim Exim | =4.64 | |
Exim Exim | =4.41 | |
Exim Exim | =4.20 | |
Exim Exim | =4.65 | |
Exim Exim | =4.53 | |
Exim Exim | =4.33 | |
Exim Exim | =4.50 | |
Exim Exim | <=4.71 | |
Exim Exim | =4.34 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.