OpenSSH GatewayPorts security bypass
| openssh-gatewayports-security-bypass (22115) |  High Risk |
Description:
OpenSSH could allow a remote attacker to bypass security restrictions. This is caused by improper handling of dynamic port forwardings when there is no listen address being specified. A remote attacker could use this vulnerability to bypass security restrictions and cause the GatewayPorts to be improperly activated.
Consequences:
Bypass Security
Remedy:
Upgrade to the latest version of OpenSSH (4.2p1 or later), available from the OpenSSH FTP Download Web page. See References.
For OpenPKG:
Refer to OpenPKG Security Advisory OpenPKG-SA-2002.010 for patch, upgrade, or suggested workaround information. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
References:
- OpenSSH FTP Download Web page: FTP page.
- ASA-2006-033: OpenSSH Multiple Vulnerabilities (SCOSA-2005.53)
- BID-14727: OpenSSH DynamicForward Inadvertent GatewayPorts Activation Vulnerability
- CVE-2005-2797: OpenSSH 4.0, and other versions before 4.2, does not properly handle dynamic port forwarding (-D option) when a listen address is not provided, which may cause OpenSSH to enable the GatewayPorts functionality.
- OpenPKG-SA-2005.019: OpenSSH
- OSVDB ID: 19142: OpenSSH Multiple X11 Channel Forwarding Leaks
- SA16686: OpenSSH Two Security Issues
- SA18661: Avaya Intuity Audix Two OpenSSH Security Issues
- SECTRACK ID: 1014845: OpenSSH May Unexpectedly Activate GatewayPorts and Also May Disclose GSSAPI Credentials in Certain Cases
Platforms Affected:
- OpenBSD OpenSSH 4.0
- OpenPKG OpenPKG 2.3
- OpenPKG OpenPKG 2.4
- OpenPKG OpenPKG CURRENT
Reported:
Sep 02, 2005
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net