CVE-2002-1644: High severity SSH Ssh2 vulnerability
Published 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.
Affected Software
15 affected components
SSH Ssh2=2.0.13
SSH Ssh2=2.1
SSH Ssh2=2.2
SSH Ssh2=2.3
SSH Ssh2=2.4
SSH Ssh2=2.5
SSH Ssh2=3.0
SSH Ssh2=3.0.1
SSH Ssh2=3.1
SSH Ssh2=3.1.1
SSH Ssh2=3.1.2
SSH Ssh2=3.1.3
SSH Ssh2=3.1.4
SSH Ssh2=3.2
SSH Ssh2=3.2.1
Remediation
Patch Available
Patch Available
Patch Available
Event History
Nov 25, 2002
CVE Published
05:00 AM
Mar 28, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2002-1644?
CVE-2002-1644 has been classified as a moderate severity vulnerability.
2
How do I fix CVE-2002-1644?
To fix CVE-2002-1644, upgrade your SSH Secure Shell to a version later than 3.2.1.
3
What vulnerabilities does CVE-2002-1644 exploit?
CVE-2002-1644 exploits the lack of a setsid call in SSH when running without a PTY, allowing privilege escalation.
4
Which versions of SSH are affected by CVE-2002-1644?
SSH Secure Shell versions from 2.0.13 to 3.2.1 are affected by CVE-2002-1644.
5
Is there a workaround for CVE-2002-1644?
A temporary workaround for CVE-2002-1644 is to disable features that allow running SSH without a PTY.