the_sut.tex 7.36 KB
 Paul Fiterau Brostean committed Jan 20, 2017 1 2 3 4 5 6 7 8 9 10 11 \section{The Secure Shell Protocol} \label{sec:ssh} The Secure Shell Protocol (or SSH) is a protocol used for secure remote login and other secure network services over an insecure network. The initial version of the protocol was superseded by a second version (SSHv2), as the former was found to contain design flaws~\cite{FutoranskyAttack} which could not be fixed without losing backwards compatibility. This work focuses on SSHv2. SSHv2 follows a client-server paradigm consisting of three components (Figure~\ref{fig:sshcomponents}): \begin{itemize} \item The \textit{transport layer protocol} (RFC 4253~\cite{rfc4253}) forms the basis for any communication between a client and a server. It provides confidentiality, integrity and server authentication as well as optional compression. \item The \textit{user authentication protocol} (RFC 4252~\cite{rfc4252}) is used to authenticate the client to the server. \item The \textit{connection protocol} (RFC 4254~\cite{rfc4254}) allows the encrypted channel to be multiplexed in different channels. These channels enable a user to run multiple processes, such as terminal emulation or file transfer, over a single SSH connection. \end{itemize}  Paul Fiterau Brostean committed Feb 08, 2017 12 13 14 15 16 Each layer has its own specific messages. The SSH protocol is interesting in that outer layers do not encapsulate inner layers. This means that different layers can interact. Hence, it makes sense to learn SSH as a whole, instead of analyzing its constituent layers independently. We review each layer, outlining the relevant messages which are later used in learning. We refer to as \textit{happy flow}, the common case of a successful operation. The SSH protocol happy flow at a high level consists of the following steps: (1) the client first establishes a TCP connection with the server, (2) the two sides negotiate encryption algorithms, and subsequently establish one-time session keys via a negotiated key exchange method, further communication is secured using these keys, (3) the client authenticates to the server by providing valid credentials and finally, (4) the client accesses services on the server like for example the terminal service. We omit the first step in our detailed description. The following steps are an integral part of each of SSH's layers. %perhaps room for figure  Paul Fiterau Brostean committed Jan 20, 2017 17 18 19 20 %Different layers are identified by their message numbers. These message numbers will form the basis of the state fuzzing. The SSH protocol is especially interesting because outer layers do not encapsulate inner layers. This means that different layers can interact. One could argue that this is a less systematic approach, in which a programmer is more likely to make state machine-related errors. \begin{figure}[!hb] \centering  Paul Fiterau Brostean committed Feb 08, 2017 21  \includegraphics[scale=0.35]{SSH_protocols.png}  Paul Fiterau Brostean committed Jan 20, 2017 22 23 24 25 26  \caption{SSH protocol components running on a TCP/IP stack.} \label{fig:sshcomponents} \end{figure} \subsection{Transport layer}\label{ssh-run-trans}  Paul Fiterau Brostean committed Feb 08, 2017 27 28 SSH provides end-to-end encryption based on pseudo-random keys which are securely negotiated as part of a \textsl{key exchange} method. Key exchange begins by the two sides exchanging their preferences for negotiable parameters relating to the actual key exchange algorithm used, as well as encryption, compression and hashing algorithms preferred and supported by either side. Preferences are sent via the \textsc{kexinit} message. Subsequently, key exchange using the negotiated algorithm takes place. Following this algorithm, one-time session keys for encryption and hashing are generated by each side, together with an identifier for the session. Diffie-Hellman is the main key exchange algorithm, and the only one required for support by the RFC. Under the Diffie-Hellman scheme, \textsc{kex30} and \textsc{kex31} are exchanged and new session keys are produced. These keys are used from the moment the \textsc{newkeys} command has been issued by both parties. A subsequent \textsc{sr\_auth} requests the authentication service. The happy flow thus consists of the succession of the three steps comprising key exchange, followed up by a successful authentication service request. The sequence is shown in Figure~\ref{fig:sshcomponents}.  Paul Fiterau Brostean committed Jan 20, 2017 29 30  \begin{figure}[!hb]  Paul Fiterau Brostean committed Feb 08, 2017 31  \includegraphics[scale=0.32]{hf-trans.pdf}  Paul Fiterau Brostean committed Jan 20, 2017 32 33 34 35  \caption{The happy flow for the transport layer.} \label{fig:sshcomponents} \end{figure}  Paul Fiterau Brostean committed Feb 08, 2017 36 37 38 39 40 41 42 \textsl{Key re-exchange}, or rekey, is a near identical process, with the difference being that instead of taking place at the beginning, it takes place once session keys are already in place. The purpose is to renew session keys so as to foil potential replay attacks. It follows the same steps as key exchange. Messages exchanged as part of it are encrypted using the old set of keys, messages exchanged afterward are encrypted using the new keys. %We consider an transport layer state machine secure if there is no path from the initial state to the point where the authentication service is invoked without exchanging and employing cryptographic keys. \subsection{Authentication layer}\label{ssh-run-auth} Once the authentication service has been summoned, authentication can commence. To this end, RFC 4252~\cite{rfc4252} defines four authentication methods (password, public-key, host-based and none). The authentication request includes a user name, service name and authentication data, which includes both the authentication method as well as the data needed to perform the actual authentication, such the password or public key. The happy flow for this layer is defined as the sequence that results in a successful authentication. The messages \textsc{ua\_pw\_ok} and \textsc{ua\_pk\_ok} achieve this for respectively password or public key authentication.  Paul Fiterau Brostean committed Jan 20, 2017 43 44 45 %We consider a user authentication layer state machine secure if there is no path from the unauthenticated state to the authenticated state without providing correct credentials. \begin{figure}[!ht]  Paul Fiterau Brostean committed Feb 08, 2017 46  \includegraphics[scale=0.45]{hf-auth.pdf}  Paul Fiterau Brostean committed Jan 20, 2017 47 48 49 50  \caption{The happy flow for the user authentication layer.} \label{fig:sshcomponents} \end{figure}  Paul Fiterau Brostean committed Jan 29, 2017 51 52   Paul Fiterau Brostean committed Feb 08, 2017 53 54 \subsection{Connection layer}\label{ssh-run-conn} Successful authentication makes available services of the Connection layer. The Connection layer enables the user to open and close channels of different types, with each type providing access to specific services. From the various services available, we focus on the remote terminal over a session channel, a standout feature of SSH. A happy flow would involve opening a session channel, \textsc{ch\_open}, requesting a terminal \textsc{ch\_request\_pty}, sending and managing data via the messages \textsc{ch\_send\_data}, \textsc{ch\_adj\_win}, \textsc{ch\_send\_eof}, and eventually closing the channel via \textsc{ch\_close}.  Paul Fiterau Brostean committed Jan 20, 2017 55 56 57 58 59 60 61  %Because the connection protocol offers a wide range of functionalities, we it is hard to define a single happy flow. Requesting a terminal is one of the main features of SSH and has therefore been selected as the happy flow. This behaviour is typically triggered by the trace \textsc{ch\_open}; \textsc{ch\_request\_pty}. Other %Its hard to define which behaviour would result in a state machine security flaw in this layer. We will therefore take a more general approach and look at unexpected state machine transitions that can point towards potential implementation flaws. %TODO Perhaps change this figure so to reflect text \begin{figure}[!ht]  Paul Fiterau Brostean committed Feb 08, 2017 62  \includegraphics[scale=0.35]{hf-conn.pdf}  Paul Fiterau Brostean committed Jan 20, 2017 63 64 65  \caption{The happy flow for the connection layer.} \label{fig:sshcomponents} \end{figure}