First published: Tue May 12 2009(Updated: )
From SquirrelMail vulnerability report: An issue was fixed that allowed arbitrary server-side code execution when SquirrelMail was configured to use the example "map_yp_alias" username mapping functionality. Credits: Niels Teusink Updated upstream patch (2009-05-21): <a href="http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4-STABLE/squirrelmail/functions/imap_general.php?r1=13549&r2=13733&view=patch">http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4-STABLE/squirrelmail/functions/imap_general.php?r1=13549&r2=13733&view=patch</a>
Affected Software | Affected Version | How to fix |
---|---|---|
SquirrelMail | >=1.4<1.4.21 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-500360 is categorized as high due to the potential for arbitrary server-side code execution.
To fix REDHAT-BUG-500360, upgrade SquirrelMail to version 1.4.21 or later to ensure the vulnerability is patched.
REDHAT-BUG-500360 affects SquirrelMail versions prior to 1.4.21 when configured to use the 'map_yp_alias' username mapping functionality.
The vulnerability in REDHAT-BUG-500360 allows for the execution of arbitrary server-side code, posing a significant security risk.
The vulnerability REDHAT-BUG-500360 was reported by Niels Teusink.