Announce: OpenSSH Vulnerable Leaks Private Crypto Keys to Hacker

source thehackernews

OpenSSH 7.1p2 has been released on 14 january 2016, but has found and fixed bug OpenSSH this bug allows exploited by hackers to force client to leak their secret private cryptographic keys thereby potentialy exposing users to Man-In-The-Middle (MITM) attacks.

Why Cause Flow happen?

 

The serious bug was actually the result of a code that enables an experimental "roaming" feature in the OpenSSH versions 5.4 to 7.1 in order to let users resume connections. 

However, The roaming feature contains two different vulnerabilities:

• An information sharing flaw (CVE-2016-0777)
• A less harmless buffer overflow flaw (CVE-2016-0778)

The vulnerability does not have any catchy name like some previous OpenSSH flaws.

Impact of the Vulnerability

 

This new feature can be exploited by hackers, who could use a malicious OpenSSH server to trick an affected client to give up the SSH keys when they try to log in.

Cyber crooks with one compromised server can secretly grab SSH private keys required to log into other systems from a user's PC, allowing them to jump from server to server.

The vulnerability, which is said to be years old, was uncovered by researchers from Qualys' security team on 11 January and the issue was fixed within three days by the OpenSSH team with the release of a patch.

Here's what OpenSSH officials said in an advisory published Thursday:

"The matching server code has never been shipped, but the client code was enabled by default and could be tricked by a malicious server into leaking client memory to the server, including private client user keys."
"The authentication of the server host key prevents exploitation by a man-in-the-middle, so this information leak is restricted to connections to malicious or compromised servers."

Who is Affected by the Serious Flaw?

 

The flaw resides in the versions 5.4 to 7.1 of the OpenSSH client, which end users use to connect to servers and not resides in versions used by servers.

The issue affects users running OpenSSH client on most modern operating systems including Linux, FreeBSD and Mac OSX, as well as it may also affect users running OpenSSH for Windows. However, users running PuTTY on Windows are safe.

So, users don't have to update OpenSSH on the server side (Droplet), but should update the OpenSSH client on their local computer.

How to Fix the Flaw?

 

The OpenSSH team patched the security flaw in version 7.1p2 on Thursday. So, users and organisations are strictly advised to patch their OpenSSH implementations immediately, as well as regenerate their SSH private keys as a precaution.

The latest builds of FreeBSD and OpenBSD have also been patched, as have Debian, Ubuntu, and RedHat Enterprise Linux (RHEL).

Since security patches and updates are being released for the affected distributions, the client-side roaming feature causing this security bug can be disabled manually in order to resolve the issue.

On OS X, Linux and BSD variants, disabling roaming feature can be done by adding a line of code to your SSH configuration.

On FreeBSD and Linux

Run the given command to add the new line to your configuration:

echo 'UseRoaming no' | sudo tee -a /etc/ssh/ssh_config

On Mac OSX 

Run the given command to add the new line to your configuration:

echo "UseRoaming no" >> ~/.ssh/config

Once this is done, you need to close any open SSH session in order for the change to be effective.

Proof-of-Concept Exploit

 

OpenSSH said they are not aware of attacks in wild exploiting this flaw, but Qualys said this issue may have already been exploited in the wild by sophisticated attackers.

Later on Thursday, Qualys published a post, including a proof-of-concept exploit code, effectively lighting a fire under every affected OpenSSH client.

The vulnerability is thought to be one of the most severe vulnerabilities discovered in the open-source software in years, and it's difficult to say how big the impact will be.

source thehackernews

Or Can Edited From Source Code For Disabling Roaming

Disabling Roaming in the Source Code:
=====================================

--- readconf.c 30 Jul 2015 00:01:34 -0000 1.239
+++ readconf.c 13 Jan 2016 23:17:23 -0000
@@ -1648,7 +1648,7 @@ initialize_options(Options * options)
options->tun_remote = -1;
options->local_command = NULL;
options->permit_local_command = -1;
- options->use_roaming = -1;
+ options->use_roaming = 0;
options->visual_host_key = -1;
options->ip_qos_interactive = -1;
options->ip_qos_bulk = -1;
@@ -1819,8 +1819,7 @@ fill_default_options(Options * options)
options->tun_remote = SSH_TUNID_ANY;
if (options->permit_local_command == -1)
options->permit_local_command = 0;
- if (options->use_roaming == -1)
- options->use_roaming = 1;
+ options->use_roaming = 0;
if (options->visual_host_key == -1)
options->visual_host_key = 0;
if (options->ip_qos_interactive == -1)
--- ssh.c 30 Jul 2015 00:01:34 -0000 1.420
+++ ssh.c 13 Jan 2016 23:17:23 -0000
@@ -1882,9 +1882,6 @@ ssh_session2(void)
fork_postauth();
}

- if (options.use_roaming)
- request_roaming();
-
return client_loop(tty_flag, tty_flag ?
options.escape_char : SSH_ESCAPECHAR_NONE, id);
}
source lwn

May be it's some OpenSSH bug, that has fixed. On slackware has upgraded to latest version, but FreeBSD first time upgraded.

Happy Reading!!! Thanks