I figured this worth mentioning since alot of us here use it and most servers are managed by it, meaning your security could be compromised.
source:http://news.cnet.com/8301-1009_3-10244691-83.html?tag=mncol
An underlying flaw in the widely used encryption protocol Open Secure Shell (OpenSSH) has been made public by researchers from the Royal Holloway, University of London.
The flaw, which lies in version 4.7 of OpenSSH on Debian/GNU Linux, allows 32 bits of encrypted text to be rendered in plaintext, according to a research team from the Royal Holloway Information Security Group (ISG).
An attacker has a one in 262,144 chance of success. ISG lead professor Kenny Patterson told CNET News sister site ZDNet UK last Monday that the flaw is more significant than previous vulnerabilities in OpenSSH.
"This is a design flaw in OpenSSH," said Patterson. "The other vulnerabilities have been more about coding errors."
According to Patterson, a man-in-the-middle attacker could sit on a network and grab blocks of encrypted text as they are sent from client to server. By retransmitting the blocks to the server, an attacker can work out the first four bytes of corresponding plaintext. The attacker can do this by counting how many bytes the attacker sends until the server generates an error message and tears down the connection, then working backward to deduce what was in the OpenSSH encryption field before encryption.
The attack relies on flaws in the RFC (Request for Comments) Internet standards that define SSH, said Patterson.
Patterson gave a talk on Monday at the IEEE Symposium on Security and Privacy in Oakland, Calif., to explain his group's research findings. The three ISG academics involved in the research were Patterson, Martin Albrecht, and Gaven Watson.
This vulnerability was first made public in November 2008 by the UK Centre for the Protection of National Infrastructure (CPNI), though full details of the flaw were not then given. According to the CPNI advisory, the OpenSSH flaw could be mitigated by IT professionals using AES (advanced encryption standard) in counter mode (CTR) to encrypt, instead of cipher-block chaining mode (CBC).
Patterson said his group had worked with OpenSSH developers to mitigate the flaw, and that OpenSSH version 5.2 contained countermeasures.
"They've fixed (OpenSSH); they've put countermeasures in place to stop our attack," said Patterson. "But the standard has not changed."
Patterson said that he did not believe this flaw had been exploited in the wild, and that to deduce a message of appreciable length could take days. In addition, proprietary SSH vendors had been informed of the issue in advance, and had put countermeasures in their code. However, Patterson added that it always takes time for system administrators to apply patches to servers and clients, no matter whether the software is open source or proprietary.
sad thing is, even though its under a BSD license all the code is available for review and they just now caught it.
(and no thats not why its called OpenSSH, take a look at the heading for the conf file)
