ID CVE-2008-5161
Summary Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1; and Client 4.0-J through 4.3.3-J and 4.0-K through 4.3.10-K; and (2) OpenSSH 4.7p1 and possibly other versions, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session via unknown vectors.
References
Vulnerable Configurations
  • OpenBSD OpenSSH 4.7p1
    cpe:2.3:a:openbsd:openssh:4.7p1
  • SSH Communications Security Tectia Client 4.0
    cpe:2.3:a:ssh:tectia_client:4.0
  • SSH Communications Security Tectia Client 4.0.1
    cpe:2.3:a:ssh:tectia_client:4.0.1
  • SSH Communications Security Tectia Client 4.0.3
    cpe:2.3:a:ssh:tectia_client:4.0.3
  • SSH Communications Security Tectia Client 4.0.4
    cpe:2.3:a:ssh:tectia_client:4.0.4
  • SSH Communications Security Tectia Client 4.0.5
    cpe:2.3:a:ssh:tectia_client:4.0.5
  • SSH Communications Security Tectia Client 4.2
    cpe:2.3:a:ssh:tectia_client:4.2
  • SSH Communications Security Tectia Client 4.2.1
    cpe:2.3:a:ssh:tectia_client:4.2.1
  • SSH Communications Security Tectia Client 4.3
    cpe:2.3:a:ssh:tectia_client:4.3
  • SSH Communications Security Tectia Client 4.3.1
    cpe:2.3:a:ssh:tectia_client:4.3.1
  • SSH Communications Security Tectia Client 4.3.1 J
    cpe:2.3:a:ssh:tectia_client:4.3.1j
  • SSH Communications Security Tectia Client 4.3.2
    cpe:2.3:a:ssh:tectia_client:4.3.2
  • SSH Communications Security SSH Tectia Client 4.3.2J
    cpe:2.3:a:ssh:tectia_client:4.3.2j
  • SSH Communications Security Tectia Client 4.3.3
    cpe:2.3:a:ssh:tectia_client:4.3.3
  • SSH Communications Security Tectia Client 4.3.4
    cpe:2.3:a:ssh:tectia_client:4.3.4
  • SSH Communications Security Tectia Client 4.3.5
    cpe:2.3:a:ssh:tectia_client:4.3.5
  • SSH Communications Security Tectia Client 4.3.6
    cpe:2.3:a:ssh:tectia_client:4.3.6
  • SSH Communications Security Tectia Client 4.3.7
    cpe:2.3:a:ssh:tectia_client:4.3.7
  • SSH Communications Security Tectia Client 4.3.8 K
    cpe:2.3:a:ssh:tectia_client:4.3.8k
  • SSH Communications Security SSH Tectia Client 4.3.9K
    cpe:2.3:a:ssh:tectia_client:4.3.9k
  • SSH Communications Security Tectia Client 4.4
    cpe:2.3:a:ssh:tectia_client:4.4
  • SSH Communications Security Tectia Client 4.4.1
    cpe:2.3:a:ssh:tectia_client:4.4.1
  • SSH Communications Security Tectia Client 4.4.2
    cpe:2.3:a:ssh:tectia_client:4.4.2
  • SSH Communications Security Tectia Client 4.4.3
    cpe:2.3:a:ssh:tectia_client:4.4.3
  • SSH Communications Security Tectia Client 4.4.4
    cpe:2.3:a:ssh:tectia_client:4.4.4
  • SSH Communications Security Tectia Client 4.4.6
    cpe:2.3:a:ssh:tectia_client:4.4.6
  • SSH Communications Security Tectia Client 4.4.7
    cpe:2.3:a:ssh:tectia_client:4.4.7
  • SSH Communications Security Tectia Client 4.4.8
    cpe:2.3:a:ssh:tectia_client:4.4.8
  • SSH Communications Security Tectia Client 4.4.9
    cpe:2.3:a:ssh:tectia_client:4.4.9
  • SSH Communications Security Tectia Client 4.4.10
    cpe:2.3:a:ssh:tectia_client:4.4.10
  • SSH Communications Security Tectia Client 4.4.11
    cpe:2.3:a:ssh:tectia_client:4.4.11
  • SSH Communications Security SSH Tectia Client 5.0.0
    cpe:2.3:a:ssh:tectia_client:5.0.0
  • SSH Communications Security SSH Tectia Client 5.0.0f
    cpe:2.3:a:ssh:tectia_client:5.0.0f
  • SSH Communications Security SSH Tectia Client 5.0.1
    cpe:2.3:a:ssh:tectia_client:5.0.1
  • SSH Communications Security SSH Tectia Client 5.0.1f
    cpe:2.3:a:ssh:tectia_client:5.0.1f
  • SSH Communications Security SSH Tectia Client 5.0.2
    cpe:2.3:a:ssh:tectia_client:5.0.2
  • SSH Communications Security SSH Tectia Client 5.0.2f
    cpe:2.3:a:ssh:tectia_client:5.0.2f
  • SSH Communications Security SSH Tectia Client 5.0.3
    cpe:2.3:a:ssh:tectia_client:5.0.3
  • SSH Communications Security SSH Tectia Client 5.0.3f
    cpe:2.3:a:ssh:tectia_client:5.0.3f
  • SSH Communications Security SSH Tectia Client 5.1.0
    cpe:2.3:a:ssh:tectia_client:5.1.0
  • SSH Communications Security SSH Tectia Client 5.1.1
    cpe:2.3:a:ssh:tectia_client:5.1.1
  • SSH Communications Security SSH Tectia Client 5.1.2
    cpe:2.3:a:ssh:tectia_client:5.1.2
  • SSH Communications Security SSH Tectia Client 5.1.3
    cpe:2.3:a:ssh:tectia_client:5.1.3
  • SSH Communications Security SSH Tectia Client 5.2.0
    cpe:2.3:a:ssh:tectia_client:5.2.0
  • SSH Communications Security SSH Tectia Client 5.2.1
    cpe:2.3:a:ssh:tectia_client:5.2.1
  • SSH Communications Security SSH Tectia Client 5.2.2
    cpe:2.3:a:ssh:tectia_client:5.2.2
  • SSH Communications Security SSH Tectia Client 5.2.3
    cpe:2.3:a:ssh:tectia_client:5.2.3
  • SSH Communications Security SSH Tectia Client 5.2.4
    cpe:2.3:a:ssh:tectia_client:5.2.4
  • SSH Communications Security SSH Tectia Client 5.3.0
    cpe:2.3:a:ssh:tectia_client:5.3.0
  • SSH Communications Security SSH Tectia Client 5.3.1
    cpe:2.3:a:ssh:tectia_client:5.3.1
  • SSH Communications Security SSH Tectia Client 5.3.2
    cpe:2.3:a:ssh:tectia_client:5.3.2
  • SSH Communications Security SSH Tectia Client 5.3.3
    cpe:2.3:a:ssh:tectia_client:5.3.3
  • SSH Communications Security SSH Tectia Client 5.3.5
    cpe:2.3:a:ssh:tectia_client:5.3.5
  • SSH Communications Security SSH Tectia Client 5.3.6
    cpe:2.3:a:ssh:tectia_client:5.3.6
  • SSH Communications Security SSH Tectia Client 5.3.7
    cpe:2.3:a:ssh:tectia_client:5.3.7
  • SSH Communications Security SSH Tectia Client 5.3.8
    cpe:2.3:a:ssh:tectia_client:5.3.8
  • SSH Communications Security SSH Tectia Client 6.0.0
    cpe:2.3:a:ssh:tectia_client:6.0.0
  • SSH Communications Security SSH Tectia Client 6.0.1
    cpe:2.3:a:ssh:tectia_client:6.0.1
  • SSH Communications Security SSH Tectia Client 6.0.2
    cpe:2.3:a:ssh:tectia_client:6.0.2
  • SSH Communications Security SSH Tectia Client 6.0.4
    cpe:2.3:a:ssh:tectia_client:6.0.3
  • SSH Communications Security SSH Tectia Client 6.0.4
    cpe:2.3:a:ssh:tectia_client:6.0.4
  • SSH Communications Security Tectia Connector 4.0.7
    cpe:2.3:a:ssh:tectia_connector:4.0.7
  • SSH Communications Security Tectia Connector 4.1.2
    cpe:2.3:a:ssh:tectia_connector:4.1.2
  • SSH Communications Security Tectia Connector 4.1.3
    cpe:2.3:a:ssh:tectia_connector:4.1.3
  • SSH Communications Security Tectia Connector 4.1.5
    cpe:2.3:a:ssh:tectia_connector:4.1.5
  • SSH Communications Security Tectia Connector 4.2.0
    cpe:2.3:a:ssh:tectia_connector:4.2.0
  • SSH Communications Security Tectia Connector 4.3.0
    cpe:2.3:a:ssh:tectia_connector:4.3.0
  • SSH Communications Security Tectia Connector 4.3.4
    cpe:2.3:a:ssh:tectia_connector:4.3.4
  • SSH Communications Security Tectia Connector 4.3.5
    cpe:2.3:a:ssh:tectia_connector:4.3.5
  • SSH Communications Security Tectia Connector 4.4.0
    cpe:2.3:a:ssh:tectia_connector:4.4.0
  • SSH Communications Security Tectia Connector 4.4.2
    cpe:2.3:a:ssh:tectia_connector:4.4.2
  • SSH Communications Security Tectia Connector 4.4.4
    cpe:2.3:a:ssh:tectia_connector:4.4.4
  • SSH Communications Security Tectia Connector 4.4.6
    cpe:2.3:a:ssh:tectia_connector:4.4.6
  • SSH Communications Security Tectia Connector 4.4.7
    cpe:2.3:a:ssh:tectia_connector:4.4.7
  • SSH Communications Security Tectia Connector 4.4.9
    cpe:2.3:a:ssh:tectia_connector:4.4.9
  • SSH Communications Security Tectia Connector 4.4.10
    cpe:2.3:a:ssh:tectia_connector:4.4.10
  • SSH Communications Security Tectia Connector 5.0.0
    cpe:2.3:a:ssh:tectia_connector:5.0.0
  • SSH Communications Security Tectia Connector 5.0.1
    cpe:2.3:a:ssh:tectia_connector:5.0.1
  • SSH Communications Security Tectia Connector 5.0.2
    cpe:2.3:a:ssh:tectia_connector:5.0.2
  • SSH Communications Security Tectia Connector 5.0.3
    cpe:2.3:a:ssh:tectia_connector:5.0.3
  • SSH Communications Security Tectia Connector 5.1.0
    cpe:2.3:a:ssh:tectia_connector:5.1.0
  • SSH Communications Security Tectia Connector 5.1.1
    cpe:2.3:a:ssh:tectia_connector:5.1.1
  • SSH Communications Security Tectia Connector 5.1.2
    cpe:2.3:a:ssh:tectia_connector:5.1.2
  • SSH Communications Security Tectia Connector 5.1.3
    cpe:2.3:a:ssh:tectia_connector:5.1.3
  • SSH Communications Security Tectia Connector 5.2.2
    cpe:2.3:a:ssh:tectia_connector:5.2.2
  • SSH Communications Security Tectia Connector 5.3.0
    cpe:2.3:a:ssh:tectia_connector:5.3.0
  • SSH Communications Security Tectia Connector 5.3.1
    cpe:2.3:a:ssh:tectia_connector:5.3.1
  • SSH Communications Security Tectia Connector 5.3.2
    cpe:2.3:a:ssh:tectia_connector:5.3.2
  • SSH Communications Security Tectia Connector 5.3.3
    cpe:2.3:a:ssh:tectia_connector:5.3.3
  • SSH Communications Security Tectia Connector 5.3.7
    cpe:2.3:a:ssh:tectia_connector:5.3.7
  • SSH Communications Security Tectia Connector 5.3.8
    cpe:2.3:a:ssh:tectia_connector:5.3.8
  • cpe:2.3:a:ssh:tectia_connectsecure:6.0.0
    cpe:2.3:a:ssh:tectia_connectsecure:6.0.0
  • cpe:2.3:a:ssh:tectia_connectsecure:6.0.1
    cpe:2.3:a:ssh:tectia_connectsecure:6.0.1
  • cpe:2.3:a:ssh:tectia_connectsecure:6.0.2
    cpe:2.3:a:ssh:tectia_connectsecure:6.0.2
  • cpe:2.3:a:ssh:tectia_connectsecure:6.0.3
    cpe:2.3:a:ssh:tectia_connectsecure:6.0.3
  • cpe:2.3:a:ssh:tectia_connectsecure:6.0.4
    cpe:2.3:a:ssh:tectia_connectsecure:6.0.4
  • SSH Communications Security Tectia Server 4.0
    cpe:2.3:a:ssh:tectia_server:4.0
  • SSH Communications Security Tectia Server 4.0.3
    cpe:2.3:a:ssh:tectia_server:4.0.3
  • SSH Communications Security Tectia Server 4.0.4
    cpe:2.3:a:ssh:tectia_server:4.0.4
  • SSH Communications Security Tectia Server 4.0.5
    cpe:2.3:a:ssh:tectia_server:4.0.5
  • SSH Communications Security Tectia Server 4.0.7
    cpe:2.3:a:ssh:tectia_server:4.0.7
  • SSH Communications Security Tectia Server 4.1.2
    cpe:2.3:a:ssh:tectia_server:4.1.2
  • SSH Communications Security Tectia Server 4.1.3
    cpe:2.3:a:ssh:tectia_server:4.1.3
  • SSH Communications Security Tectia Server 4.1.5
    cpe:2.3:a:ssh:tectia_server:4.1.5
  • SSH Communications Security Tectia Server 4.2.0
    cpe:2.3:a:ssh:tectia_server:4.2.0
  • SSH Communications Security Tectia Server 4.2.1
    cpe:2.3:a:ssh:tectia_server:4.2.1
  • SSH Communications Security Tectia Server 4.2.2
    cpe:2.3:a:ssh:tectia_server:4.2.2
  • SSH Communications Security Tectia Server 4.3
    cpe:2.3:a:ssh:tectia_server:4.3
  • SSH Communications Security Tectia Server 4.3.0
    cpe:2.3:a:ssh:tectia_server:4.3.0
  • SSH Communications Security Tectia Server 4.3.1
    cpe:2.3:a:ssh:tectia_server:4.3.1
  • SSH Communications Security Tectia Server 4.3.2
    cpe:2.3:a:ssh:tectia_server:4.3.2
  • SSH Communications Security Tectia Server 4.3.3
    cpe:2.3:a:ssh:tectia_server:4.3.3
  • SSH Communications Security Tectia Server 4.3.4
    cpe:2.3:a:ssh:tectia_server:4.3.4
  • SSH Communications Security Tectia Server 4.3.5
    cpe:2.3:a:ssh:tectia_server:4.3.5
  • SSH Communications Security Tectia Server 4.3.6
    cpe:2.3:a:ssh:tectia_server:4.3.6
  • SSH Communications Security Tectia Server 4.3.7
    cpe:2.3:a:ssh:tectia_server:4.3.7
  • SSH Communications Security Tectia Server 4.4
    cpe:2.3:a:ssh:tectia_server:4.4
  • SSH Communications Security Tectia Server 4.4.0
    cpe:2.3:a:ssh:tectia_server:4.4.0
  • SSH Communications Security Tectia Server 4.4.1
    cpe:2.3:a:ssh:tectia_server:4.4.1
  • SSH Communications Security Tectia Server 4.4.2
    cpe:2.3:a:ssh:tectia_server:4.4.2
  • SSH Communications Security Tectia Server 4.4.4
    cpe:2.3:a:ssh:tectia_server:4.4.4
  • SSH Communications Security Tectia Server 4.4.5
    cpe:2.3:a:ssh:tectia_server:4.4.5
  • SSH Communications Security Tectia Server 4.4.6
    cpe:2.3:a:ssh:tectia_server:4.4.6
  • SSH Communications Security Tectia Server 4.4.7
    cpe:2.3:a:ssh:tectia_server:4.4.7
  • SSH Communications Security Tectia Server 4.4.8
    cpe:2.3:a:ssh:tectia_server:4.4.8
  • SSH Communications Security Tectia Server 4.4.9
    cpe:2.3:a:ssh:tectia_server:4.4.9
  • SSH Communications Security Tectia Server 4.4.10
    cpe:2.3:a:ssh:tectia_server:4.4.10
  • SSH Communications Security Tectia Server 4.4.11
    cpe:2.3:a:ssh:tectia_server:4.4.11
  • SSH Communications Security Tectia Server 5.0.0
    cpe:2.3:a:ssh:tectia_server:5.0.0
  • SSH Communications Security Tectia Server 5.0.1
    cpe:2.3:a:ssh:tectia_server:5.0.1
  • SSH Communications Security Tectia Server 5.0.2
    cpe:2.3:a:ssh:tectia_server:5.0.2
  • SSH Communications Security Tectia Server 5.0.3
    cpe:2.3:a:ssh:tectia_server:5.0.3
  • SSH Communications Security Tectia Server 5.1.0
    cpe:2.3:a:ssh:tectia_server:5.1.0
  • SSH Communications Security Tectia Server 5.1.1
    cpe:2.3:a:ssh:tectia_server:5.1.1
  • cpe:2.3:a:ssh:tectia_server:5.1.1:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.1.1:-:ibm_zos
  • SSH Communications Security Tectia Server 5.1.2
    cpe:2.3:a:ssh:tectia_server:5.1.2
  • SSH Communications Security Tectia Server 5.1.3
    cpe:2.3:a:ssh:tectia_server:5.1.3
  • SSH Communications Security Tectia Server 5.2.0
    cpe:2.3:a:ssh:tectia_server:5.2.0
  • cpe:2.3:a:ssh:tectia_server:5.2.0:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.2.0:-:ibm_zos
  • cpe:2.3:a:ssh:tectia_server:5.2.1:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.2.1:-:ibm_zos
  • SSH Communications Security Tectia Server 5.2.2
    cpe:2.3:a:ssh:tectia_server:5.2.2
  • cpe:2.3:a:ssh:tectia_server:5.2.2:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.2.2:-:ibm_zos
  • SSH Communications Security Tectia Server 5.2.3
    cpe:2.3:a:ssh:tectia_server:5.2.3
  • SSH Communications Security Tectia Server 5.2.4
    cpe:2.3:a:ssh:tectia_server:5.2.4
  • SSH Communications Security SSH Tectia Server 5.3.0
    cpe:2.3:a:ssh:tectia_server:5.3.0
  • cpe:2.3:a:ssh:tectia_server:5.3.0:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.3.0:-:ibm_zos
  • SSH Communications Security SSH Tectia Server 5.3.1
    cpe:2.3:a:ssh:tectia_server:5.3.1
  • SSH Communications Security SSH Tectia Server 5.3.2
    cpe:2.3:a:ssh:tectia_server:5.3.2
  • SSH Communications Security SSH Tectia Server 5.3.3
    cpe:2.3:a:ssh:tectia_server:5.3.3
  • SSH Communications Security SSH Tectia Server 5.3.4
    cpe:2.3:a:ssh:tectia_server:5.3.4
  • SSH Communications Security SSH Tectia Server 5.3.5
    cpe:2.3:a:ssh:tectia_server:5.3.5
  • SSH Communications Security SSH Tectia Server 5.3.6
    cpe:2.3:a:ssh:tectia_server:5.3.6
  • SSH Communications Security SSH Tectia Server 5.3.7
    cpe:2.3:a:ssh:tectia_server:5.3.7
  • SSH Communications Security SSH Tectia Server 5.3.8
    cpe:2.3:a:ssh:tectia_server:5.3.8
  • cpe:2.3:a:ssh:tectia_server:5.4.0:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.4.0:-:ibm_zos
  • cpe:2.3:a:ssh:tectia_server:5.4.1:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.4.1:-:ibm_zos
  • cpe:2.3:a:ssh:tectia_server:5.4.2:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.4.2:-:ibm_zos
  • cpe:2.3:a:ssh:tectia_server:5.5.0:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.5.0:-:ibm_zos
  • cpe:2.3:a:ssh:tectia_server:5.5.1:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:5.5.1:-:ibm_zos
  • SSH Communications Security SSH Tectia Server 6.0.0
    cpe:2.3:a:ssh:tectia_server:6.0.0
  • cpe:2.3:a:ssh:tectia_server:6.0.0:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:6.0.0:-:ibm_zos
  • SSH Communications Security SSH Tectia Server 6.0.1
    cpe:2.3:a:ssh:tectia_server:6.0.1
  • cpe:2.3:a:ssh:tectia_server:6.0.1:-:ibm_zos
    cpe:2.3:a:ssh:tectia_server:6.0.1:-:ibm_zos
  • SSH Communications Security SSH Tectia Server 6.0.2
    cpe:2.3:a:ssh:tectia_server:6.0.2
  • SSH Communications Security SSH Tectia Server 6.0.3
    cpe:2.3:a:ssh:tectia_server:6.0.3
  • SSH Communications Security SSH Tectia Server 6.0.4
    cpe:2.3:a:ssh:tectia_server:6.0.4
  • SSH Communications Security Tectia Server 6.0.4 for Linux on IBM System Z
    cpe:2.3:a:ssh:tectia_server:6.0.4:-:linux_ibm_zos
CVSS
Base: 2.6 (as of 08-08-2014 - 16:54)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK HIGH NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family Misc.
    NASL id OPENSSH_PLAINTEXT_RECOVERY.NASL
    description The version of OpenSSH running on the remote host has an information disclosure vulnerability. A design flaw in the SSH specification could allow a man-in-the-middle attacker to recover up to 32 bits of plaintext from an SSH-protected connection in the standard configuration. An attacker could exploit this to gain access to sensitive information.
    last seen 2019-02-21
    modified 2018-07-16
    plugin id 44065
    published 2011-09-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=44065
    title OpenSSH < 5.2 CBC Plaintext Disclosure
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2009-006.NASL
    description The remote host is running a version of Mac OS X 10.5 that does not have Security Update 2009-006 applied. This security update contains fixes for the following products : - AFP Client - Adaptive Firewall - Apache - Apache Portable Runtime - ATS - Certificate Assistant - CoreGraphics - CUPS - Dictionary - DirectoryService - Disk Images - Event Monitor - fetchmail - FTP Server - Help Viewer - International Components for Unicode - IOKit - IPSec - libsecurity - libxml - OpenLDAP - OpenSSH - PHP - QuickDraw Manager - QuickLook - FreeRADIUS - Screen Sharing - Spotlight - Subversion
    last seen 2019-02-21
    modified 2018-07-16
    plugin id 42433
    published 2009-11-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=42433
    title Mac OS X Multiple Vulnerabilities (Security Update 2009-006)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2009-1287.NASL
    description Updated openssh packages that fix a security issue, a bug, and add enhancements are now available for Red Hat Enterprise Linux 5. This update has been rated as having low security impact by the Red Hat Security Response Team. OpenSSH is OpenBSD's SSH (Secure Shell) protocol implementation. These packages include the core files necessary for both the OpenSSH client and server. A flaw was found in the SSH protocol. An attacker able to perform a man-in-the-middle attack may be able to obtain a portion of plain text from an arbitrary ciphertext block when a CBC mode cipher was used to encrypt SSH communication. This update helps mitigate this attack: OpenSSH clients and servers now prefer CTR mode ciphers to CBC mode, and the OpenSSH server now reads SSH packets up to their full possible length when corruption is detected, rather than reporting errors early, reducing the possibility of successful plain text recovery. (CVE-2008-5161) This update also fixes the following bug : * the ssh client hung when trying to close a session in which a background process still held tty file descriptors open. With this update, this so-called 'hang on exit' error no longer occurs and the ssh client closes the session immediately. (BZ#454812) In addition, this update adds the following enhancements : * the SFTP server can now chroot users to various directories, including a user's home directory, after log in. A new configuration option -- ChrootDirectory -- has been added to '/etc/ssh/sshd_config' for setting this up (the default is not to chroot users). Details regarding configuring this new option are in the sshd_config(5) manual page. (BZ#440240) * the executables which are part of the OpenSSH FIPS module which is being validated will check their integrity and report their FIPS mode status to the system log or to the terminal. (BZ#467268, BZ#492363) All OpenSSH users are advised to upgrade to these updated packages, which contain backported patches to resolve these issues and add these enhancements. After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 40837
    published 2009-09-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=40837
    title RHEL 5 : openssh (RHSA-2009:1287)
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS9_122300.NASL
    description SunOS 5.9: Kernel Patch. Date this patch was last updated by Sun : Nov/03/11
    last seen 2018-09-01
    modified 2016-12-09
    plugin id 24858
    published 2007-03-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=24858
    title Solaris 9 (sparc) : 122300-61
  • NASL family Misc.
    NASL id SSH_CBC_SUPPORTED_CIPHERS.NASL
    description The SSH server is configured to support Cipher Block Chaining (CBC) encryption. This may allow an attacker to recover the plaintext message from the ciphertext. Note that this plugin only checks for the options of the SSH server and does not check for vulnerable software versions.
    last seen 2019-02-21
    modified 2018-07-30
    plugin id 70658
    published 2013-10-28
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70658
    title SSH Server CBC Mode Ciphers Enabled
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS10_140774.NASL
    description SunOS 5.10: sshd patch. Date this patch was last updated by Sun : Mar/19/09
    last seen 2018-09-01
    modified 2018-08-13
    plugin id 36806
    published 2009-04-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=36806
    title Solaris 10 (sparc) : 140774-03
  • NASL family Misc.
    NASL id SUNSSH_PLAINTEXT_RECOVERY.NASL
    description The version of SunSSH running on the remote host has an information disclosure vulnerability. A design flaw in the SSH specification could allow a man-in-the-middle attacker to recover up to 32 bits of plaintext from an SSH-protected connection in the standard configuration. An attacker could exploit this to gain access to sensitive information. Note that this version of SunSSH is also prone to several additional issues but Nessus did not test for them.
    last seen 2019-02-21
    modified 2018-07-31
    plugin id 55992
    published 2011-08-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=55992
    title SunSSH < 1.1.1 / 1.3 CBC Plaintext Disclosure
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS9_X86_122301.NASL
    description SunOS 5.9_x86: Kernel Patch. Date this patch was last updated by Sun : Nov/03/11
    last seen 2018-09-02
    modified 2016-12-09
    plugin id 24861
    published 2007-03-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=24861
    title Solaris 9 (x86) : 122301-61
  • NASL family F5 Networks Local Security Checks
    NASL id F5_BIGIP_SOL14609.NASL
    description Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1; and Client 4.0-J through 4.3.3-J and 4.0-K through 4.3.10-K; and (2) OpenSSH 4.7p1 and possibly other versions, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session by way of unknown vectors. (CVE-2008-5161)
    last seen 2019-02-21
    modified 2019-01-04
    plugin id 78153
    published 2014-10-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78153
    title F5 Networks BIG-IP : OpenSSH vulnerability (K14609)
  • NASL family AIX Local Security Checks
    NASL id AIX_OPENSSH_ADVISORY.NASL
    description The version of OpenSSH running on the remote host is affected by the following vulnerabilities : - X11 man-in-the-middle attack: When attempting to bind(2) to a port that has previously been bound with SO_REUSEADDR set, most operating systems check that either the effective user-id matches the previous bind (common on BSD-derived systems) or that the bind addresses do not overlap. When the sshd_config(5) option X11UseLocalhost has been set to 'no' - an attacker may establish a more-specific bind, which will be used in preference to sshd's wildcard listener. (CVE-2008-3259) - Plaintext Recovery Attack Against SSH: If exploited, this attack can potentially allow an attacker to recover up to 32 bits of plaintext from an arbitrary block of ciphertext from a connection secured using the SSH protocol in the standard configuration. If OpenSSH is used in the standard configuration, then the attacker's success probability for recovering 32 bits of plaintext is 2^{-18}. A variant of the attack against OpenSSH in the standard configuration can verifiably recover 14 bits of plaintext with probability 2^{-14}. The success probability of the attack for other implementations of SSH is not known. (CVE-2008-5161)
    last seen 2019-02-21
    modified 2018-07-17
    plugin id 73557
    published 2014-04-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73557
    title AIX OpenSSH Advisory: openssh_advisory.asc
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20090902_OPENSSH_ON_SL5_X.NASL
    description CVE-2008-5161 OpenSSH: Plaintext Recovery Attack against CBC ciphers A flaw was found in the SSH protocol. An attacker able to perform a man-in-the-middle attack may be able to obtain a portion of plain text from an arbitrary ciphertext block when a CBC mode cipher was used to encrypt SSH communication. This update helps mitigate this attack: OpenSSH clients and servers now prefer CTR mode ciphers to CBC mode, and the OpenSSH server now reads SSH packets up to their full possible length when corruption is detected, rather than reporting errors early, reducing the possibility of successful plain text recovery. (CVE-2008-5161) This update also fixes the following bug : - the ssh client hung when trying to close a session in which a background process still held tty file descriptors open. With this update, this so-called 'hang on exit' error no longer occurs and the ssh client closes the session immediately. (BZ#454812) In addition, this update adds the following enhancements : - the SFTP server can now chroot users to various directories, including a user's home directory, after log in. A new configuration option -- ChrootDirectory -- has been added to '/etc/ssh/sshd_config' for setting this up (the default is not to chroot users). Details regarding configuring this new option are in the sshd_config(5) manual page. (BZ#440240) - the executables which are part of the OpenSSH FIPS module which is being validated will check their integrity and report their FIPS mode status to the system log or to the terminal. (BZ#467268, BZ#492363) After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically. Note: fipscheck update needed for dependencies.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 60657
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=60657
    title Scientific Linux Security Update : openssh on SL5.x i386/x86_64
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS10_X86_140775.NASL
    description SunOS 5.10_x86: sshd patch. Date this patch was last updated by Sun : Mar/19/09
    last seen 2018-09-01
    modified 2018-08-13
    plugin id 36559
    published 2009-04-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=36559
    title Solaris 10 (x86) : 140775-03
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201405-06.NASL
    description The remote host is affected by the vulnerability described in GLSA-201405-06 (OpenSSH: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in OpenSSH. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could execute arbitrary code, cause a Denial of Service condition, obtain sensitive information, or bypass environment restrictions. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-13
    plugin id 73958
    published 2014-05-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73958
    title GLSA-201405-06 : OpenSSH: Multiple vulnerabilities
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2009-1287.NASL
    description Updated openssh packages that fix a security issue, a bug, and add enhancements are now available for Red Hat Enterprise Linux 5. This update has been rated as having low security impact by the Red Hat Security Response Team. OpenSSH is OpenBSD's SSH (Secure Shell) protocol implementation. These packages include the core files necessary for both the OpenSSH client and server. A flaw was found in the SSH protocol. An attacker able to perform a man-in-the-middle attack may be able to obtain a portion of plain text from an arbitrary ciphertext block when a CBC mode cipher was used to encrypt SSH communication. This update helps mitigate this attack: OpenSSH clients and servers now prefer CTR mode ciphers to CBC mode, and the OpenSSH server now reads SSH packets up to their full possible length when corruption is detected, rather than reporting errors early, reducing the possibility of successful plain text recovery. (CVE-2008-5161) This update also fixes the following bug : * the ssh client hung when trying to close a session in which a background process still held tty file descriptors open. With this update, this so-called 'hang on exit' error no longer occurs and the ssh client closes the session immediately. (BZ#454812) In addition, this update adds the following enhancements : * the SFTP server can now chroot users to various directories, including a user's home directory, after log in. A new configuration option -- ChrootDirectory -- has been added to '/etc/ssh/sshd_config' for setting this up (the default is not to chroot users). Details regarding configuring this new option are in the sshd_config(5) manual page. (BZ#440240) * the executables which are part of the OpenSSH FIPS module which is being validated will check their integrity and report their FIPS mode status to the system log or to the terminal. (BZ#467268, BZ#492363) All OpenSSH users are advised to upgrade to these updated packages, which contain backported patches to resolve these issues and add these enhancements. After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 43781
    published 2010-01-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=43781
    title CentOS 5 : openssh (CESA-2009:1287)
oval via4
accepted 2013-04-29T04:12:52.731-04:00
class vulnerability
contributors
  • name Aharon Chernin
    organization SCAP.com, LLC
  • name Dragos Prisaca
    organization G2, Inc.
definition_extensions
  • comment The operating system installed on the system is Red Hat Enterprise Linux 5
    oval oval:org.mitre.oval:def:11414
  • comment The operating system installed on the system is CentOS Linux 5.x
    oval oval:org.mitre.oval:def:15802
  • comment Oracle Linux 5.x
    oval oval:org.mitre.oval:def:15459
description session via unknown vectors.
family unix
id oval:org.mitre.oval:def:11279
status accepted
submitted 2010-07-09T03:56:16-04:00
title to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session via unknown vectors.
version 18
redhat via4
advisories
bugzilla
id 472068
title CVE-2008-5161 OpenSSH: Plaintext Recovery Attack against CBC ciphers
oval
AND
  • comment Red Hat Enterprise Linux 5 is installed
    oval oval:com.redhat.rhba:tst:20070331001
  • OR
    • AND
      • comment openssh is earlier than 0:4.3p2-36.el5
        oval oval:com.redhat.rhsa:tst:20091287002
      • comment openssh is signed with Red Hat redhatrelease key
        oval oval:com.redhat.rhsa:tst:20070540003
    • AND
      • comment openssh-askpass is earlier than 0:4.3p2-36.el5
        oval oval:com.redhat.rhsa:tst:20091287006
      • comment openssh-askpass is signed with Red Hat redhatrelease key
        oval oval:com.redhat.rhsa:tst:20070540009
    • AND
      • comment openssh-clients is earlier than 0:4.3p2-36.el5
        oval oval:com.redhat.rhsa:tst:20091287004
      • comment openssh-clients is signed with Red Hat redhatrelease key
        oval oval:com.redhat.rhsa:tst:20070540007
    • AND
      • comment openssh-server is earlier than 0:4.3p2-36.el5
        oval oval:com.redhat.rhsa:tst:20091287008
      • comment openssh-server is signed with Red Hat redhatrelease key
        oval oval:com.redhat.rhsa:tst:20070540005
rhsa
id RHSA-2009:1287
released 2009-09-01
severity Low
title RHSA-2009:1287: openssh security, bug fix, and enhancement update (Low)
rpms
  • openssh-0:4.3p2-36.el5
  • openssh-askpass-0:4.3p2-36.el5
  • openssh-clients-0:4.3p2-36.el5
  • openssh-server-0:4.3p2-36.el5
refmap via4
apple APPLE-SA-2009-11-09-1
bid 32319
bugtraq
  • 20081121 OpenSSH security advisory: cbc.adv
  • 20081123 Revised: OpenSSH security advisory: cbc.adv
cert-vn VU#958563
confirm
hp
  • HPSBMA02447
  • SSRT090062
misc
osvdb
  • 49872
  • 50035
  • 50036
sectrack
  • 1021235
  • 1021236
  • 1021382
secunia
  • 32740
  • 32760
  • 32833
  • 33121
  • 33308
  • 34857
  • 36558
sunalert 247186
vupen
  • ADV-2008-3172
  • ADV-2008-3173
  • ADV-2008-3409
  • ADV-2009-1135
  • ADV-2009-3184
xf openssh-sshtectia-cbc-info-disclosure(46620)
statements via4
contributor Joshua Bressers
lastmodified 2009-09-02
organization Red Hat
statement This issue was addressed for Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1287.html After reviewing the upstream fix for this issue, Red Hat does not intend to address this flaw in Red Hat Enterprise Linux 3 or 4 at this time.
Last major update 02-01-2017 - 21:59
Published 19-11-2008 - 12:30
Last modified 11-10-2018 - 16:54
Back to Top