A locally exploitable privilege escalation vulnerability exists in SSH Secure Shell versions 2.0.13 - 3.2.1.
Secure Shell for Servers, developed by SSH Communications Security, does not properly remove the child process from the master process group after non-interactive command execution. Quoting from the SSH Communications Security Advisory:
When used in non-interactive connections, a defect in process grouping
of SSH Secure Shell processes may allow malicious activity. If
executing a command without a pty (including running commands and
subsystems) the child process remains in the process group of the
On platforms relying on getlogin() (mainly the different BSD variants)
malicious users can at least send misleading messages to syslog and
others applications (getlogin() call will return "root").
For more details, please see the SSH Communications Security Advisory.
A local attacker may be able to gain elevated privileges.
Upgrade your software. Note that both Secure Shell for Servers and Secure Shell for Workstations need to be updated to eliminate this vulnerability.
Vendor| Status| Date Notified| Date Updated
SSH Communications Security| | -| 14 May 2003
Hewlett-Packard Company| | -| 29 May 2008
If you are a vendor and your product is affected, let us know.
Group | Score | Vector
Base | N/A | N/A
Temporal | N/A | N/A
Environmental | N/A | N/A
Thanks to Logan Gabriel for reporting this vulnerability.
This document was written by Ian A Finlay.