CVE-2017-7692: Input Validation

Published Apr 20, 2017
·
Updated

SquirrelMail 1.4.22 (and other versions before 201704270200-SVN) allows post-authentication remote code execution via a sendmail.cf file that is mishandled in a popen call. It's possible to exploit this vulnerability to execute arbitrary shell commands on the remote server. The problem is in the DeliverSendMail.class.php with the initStream function that uses escapeshellcmd() to sanitize the sendmail command before executing it. The use of escapeshellcmd() is not correct in this case since it doesn't escape whitespaces, allowing the injection of arbitrary command parameters. The problem is in -f$envelopefrom within the sendmail command line. Hence, if the target server uses sendmail and SquirrelMail is configured to use it as a command-line program, it's possible to trick sendmail into using an attacker-provided configuration file that triggers the execution of an arbitrary command. For exploitation, the attacker must upload a sendmail.cf file as an email attachment, and inject the sendmail.cf filename with the -C option within the "Options > Personal Informations > Email Address" setting.

Affected Software

1 affected component
Squirrelmail Squirrelmail=1.4.22

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade SquirrelMail to a version that resolves this vulnerability.

    Fixed in 1.4.22
  2. Upgrade

    Upgrade SquirrelMail to a version that resolves this vulnerability.

    Patch 20170427_0200-SVN
  3. Upgrade

    Upgrade SquirrelMail to a version that resolves this vulnerability.

    Fixed in 20170427_0200-SVNPatch 20170427_0200-SVN

Event History

Apr 20, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:59 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-7692?

CVE-2017-7692 has a critical severity rating due to the possibility of post-authentication remote code execution.

2

How do I fix CVE-2017-7692?

To fix CVE-2017-7692, upgrade SquirrelMail to version 1.4.22 or later, ensuring you apply any available patches.

3

What versions of SquirrelMail are vulnerable to CVE-2017-7692?

SquirrelMail versions before 20170427_0200-SVN, including 1.4.22, are vulnerable to CVE-2017-7692.

4

What types of attacks can exploit CVE-2017-7692?

CVE-2017-7692 can be exploited to execute arbitrary shell commands on the remote server after authentication.

5

Is CVE-2017-7692 specific to any operating system?

CVE-2017-7692 affects SquirrelMail software regardless of the underlying operating system, as long as it is running an affected version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203