First published: Mon Nov 25 2002(Updated: )
SSH Secure Shell for Servers and SSH Secure Shell for Workstations 2.0.13 through 3.2.1, when running without a PTY, does not call setsid to remove the child process from the process group of the parent process, which allows attackers to gain certain privileges.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SSH (Secure Shell) | =2.0.13 | |
SSH (Secure Shell) | =2.1 | |
SSH (Secure Shell) | =2.2 | |
SSH (Secure Shell) | =2.3 | |
SSH (Secure Shell) | =2.4 | |
SSH (Secure Shell) | =2.5 | |
SSH (Secure Shell) | =3.0 | |
SSH (Secure Shell) | =3.0.1 | |
SSH (Secure Shell) | =3.1 | |
SSH (Secure Shell) | =3.1.1 | |
SSH (Secure Shell) | =3.1.2 | |
SSH (Secure Shell) | =3.1.3 | |
SSH (Secure Shell) | =3.1.4 | |
SSH (Secure Shell) | =3.2 | |
SSH (Secure Shell) | =3.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2002-1644 has been classified as a moderate severity vulnerability.
To fix CVE-2002-1644, upgrade your SSH Secure Shell to a version later than 3.2.1.
CVE-2002-1644 exploits the lack of a setsid call in SSH when running without a PTY, allowing privilege escalation.
SSH Secure Shell versions from 2.0.13 to 3.2.1 are affected by CVE-2002-1644.
A temporary workaround for CVE-2002-1644 is to disable features that allow running SSH without a PTY.