Vulnerability Note VU#502328

SquirrelMail vulnerable to command injection because of flawed input checking in S/MIME plug-in

Original Release date: 09 Feb 2005 | Last revised: 10 Feb 2005


SquirrelMail contains a flaw in its S/MIME plug-in certificate handling routines which may allow arbitrary code to be remotely executed.


From the SquirrelMail web page:

    SquirrelMail is a standards-based webmail package written in PHP4. It includes built-in pure PHP support for the IMAP and SMTP protocols, and all pages render in pure HTML 4.0 (with no JavaScript required) for maximum compatibility across browsers. It has very few requirements and is very easy to configure and install. SquirrelMail has all the functionality you would want from an email client, including strong MIME support, address books, and folder manipulation.

SquirrelMail's input handling contains a flaw that may allow remote attackers to execute arbitrary code with elevated privileges. The S/MIME plug-in fails to check the $cert variable, which contains user-supplied data, before using the variable in a call to exec().


A remote attacker may be able to supply arbitrary code to be executed in the call to exec() with the privileges of the web server.


Apply an update
SquirrelMail has released an updated version of the S/MIME plug-in that is not affected by this flaw. Version 0.6 (or later) does not contain this flaw and can be obtained from the SquirrelMail S/MIME plug-in page.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
SquirrelMail Project TeamAffected08 Feb 200509 Feb 2005
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



Thanks to iDefense for reporting this vulnerability, who in turn credit Karol Wiesek with the discovery of the flaw.

This document was written by Ken MacInnis based primarily on information from iDefense Inc.

Other Information

  • CVE IDs: CAN-2005-0239
  • Date Public: 07 Feb 2005
  • Date First Published: 09 Feb 2005
  • Date Last Updated: 10 Feb 2005
  • Severity Metric: 4.91
  • Document Revision: 14


If you have feedback, comments, or additional information about this vulnerability, please send us email.