Practical Pitfalls for Security in OPC UA

Practical Pitfalls for Security in OPC UA Alessandro Erba∗y, Anne Muller¨ ∗y, Nils Ole Tippenhauer∗ ∗CISPA Helmholtz Center for Information Security, ySaarbrucken¨ Graduate School of Computer Science, Saarland University [alessandro.erba, anne.mueller, tippenhauer]@cispa.de Abstract—In 2006, the OPC Foundation released the first (i.e. client impersonation), and iii) Middleperson attacks. For specification for OPC Unified Architecture protocol, one of example, an attacker can feed wrong information to clients the industrial protocols that promises security features such (Rogue Server attack), eavesdrop, and change values which as authentication, authorization, integrity, and confidentiality. Challenges in the practical adoption of those security features can directly alter the physical process (Rogue Client attack), by product vendors, libraries implementing the standard, and or both (Middleperson attack). In 2017, the German Federal end-users were not investigated so far. Office for Information Security (BSI) released the ‘OPC UA In this work, we systematically investigate practical challenges Security Analysis’ [2], reporting that ‘No systematic errors to configure OPC UA securely. In particular, we review 48 could be detected’ in the OPC UA standard. In addition, the artifacts consisting of products and libraries for OPC UA and show that 38 out of the 48 artifacts have one (or more) security BSI recommended using only ‘Sign’ or ‘SignAndEncrypt’ as issue. In particular, we show that 7 OPC UA artifacts do security mode, with ‘Basic256Sha256’ as security policy, and not support the security features of the protocol at all. In configure a user authentication mechanism. addition, 31 artifacts that partially feature OPC UA security rely Nevertheless, there seem to be significant challenges to set on incomplete libraries and come with misleading instructions. up secure OPC UA deployments in practice. In [3], Dahlmanns Consequently, relying on those products and libraries will result in vulnerable implementations of OPC UA security features. We et al. perform a scan for OPC UA servers reachable over design, implement and demonstrate attacks in which the attacker the Internet and find that 92% of the reachable deployments can steal credentials exchanged between victims, eavesdrop on show issues with security configuration. Among those, 44% process information, manipulate the physical process through of the servers are accessible without any authentication re- sensor values and actuator commands, and prevent the detection quirements. To mitigate that issue, the authors suggest (similar of anomalies in the physical process. to [2]) to disable insecure security modes and policies and enforce user authentication. Their findings demonstrate that I. INTRODUCTION such suggestions are still not applied in a significant number Interconnection of industrial components carries security of deployments. The authors believe that this is due to the concerns that need to be addressed at different levels to configuration complexity of the OPC UA security features. allow secure industrial plants. One among the others is the In this work, we systematically investigate practical chal- security of the communication protocol adopted for Machine lenges to configure OPC UA in a secure way and prevent to Machine (M2M) communication. In 2006, the OPC Foun- the three attacks outlined above. In particular, we show that dation released the first specification for the OPC Unified many OPC UA products have missing support for security Architecture (OPC UA) protocol [1], an industrial protocol that features of the protocol. In addition, products that claim to promises security features such as authentication, authoriza- feature OPC UA security rely on libraries that are incomplete, tion, integrity, and confidentiality. OPC UA is a client/server difficult to use and provide instructions that lead to insecure architecture, e.g., in an ICS the OPC UA server is running on settings. Lastly, we also show that several popular OPC a Programmable Logic Controller (PLC) to publish industrial UA libraries provide vulnerable implementations of OPC UA arXiv:2104.06051v1 [cs.CR] 13 Apr 2021 process sensor readings and control its state. Those values can security features. be read and modified by an OPC UA client running on other To assess the vulnerability of available libraries, we cre- industrial devices or end-user systems. ate a framework that implements the three proposed attacks Although OPC UA provides features to ensure security (i.e. Rogue Server, Rogue Client, Middleperson). For each and confidentiality properties, they do not work out of the library, we set up a client and/or server application using box. OPC UA requires a correct configuration to guaran- protocol options that can be expected to provide a secured tee secure communication. For example, OPC UA specifies OPC UA instance, and then attack that system. For cases where a number of alternative securityModes (i.e., configurations the attacks succeed, we further investigate the cause for the for application authentication and encryption ranging from vulnerability. In particular, we show that Middleperson attacks ‘None’ to ‘SignAndEncrypt’), securityPolicies (i.e., algorithms are possible if vulnerable servers and clients are present in used for asymmetric encryption ranging from ‘None’ to the same network, and such attacks allow to manipulate the ‘Basic256Sha256’) and UserIdentityToken (i.e., configurations process and prevent reliable control of the system. Surpris- for user authentication). The main attacks to mitigate are i) ingly, we find that even recovery of plaintext credentials from Rogue Server (i.e. server impersonation), ii) Rogue Client intercepted encrypted communications is easily possible with our Rogue Server and Middleperson attacks. This finding is in contrast to prior work [4], where the authors perform a Middleperson attack on OPC UA applications and conclude that it is impossible to recover user passwords in OPC UA systems (even with security mode ‘None’). Contributions. We summarize our contributions as follows • We systematically analyze proprietary products and identify reoccurring issues with the availability, and setup instructions for OPC UA security features • We systematically analyze available libraries and identify reoccurring issues with the implementation of security features • We demonstrate the feasibility of the identified attacks by implementing all three attacks with a proof-of-concept application (we plan to release a proof of concept of our framework as open-source) The remainder of this work is organized as follows. In II we (a) (b) present the details of the OPC UA protocol. In III we present Fig. 1. Figure (a) gives an overview over the connection establishment the system and attacker model, as well as the approach we use procedure between client and server. The server provides a list of endpoints, to conduct our research. In IV we explain how we build the where each endpoint consist of a Security Mode, a Security Policy and a User Identity Token. The client selects which endpoint it wants to connect to. If framework that we use to analyze the available libraries. In the mode Sign or SignAndEncrypt is chosen the server and client each have V we report the results of our research. A discussion of our to send their public certificate along with the endpoint to establish the secure findings is presented in VI, followed by conclusions in VIII. channel. Figure (b) shows the options available for the endpoint configuration. The Security Mode, Security Policy and User Identity Token can be chosen independently from each other. II. BACKGROUND In this section, we present the background related to the OPC UA protocol and its security features. OPC UA features None, Basic128Rsa15 (Deprecated), Basic256 (Deprecated), several options to change the level of security achieved for a Aes128-Sha256-RsaOaep, Basic256Sha256, Aes256-Sha256- connection. RsaPss. Finally, the UserIdentityToken defines the supported user authentication methods for an endpoint: Anonymous (no A. OPC Unified Architecture user authentication), Username&Password, Certificate [5]. OPC UA [1] is an industrial communication protocol devel- When initiating a connection, the client can choose the end- oped by the OPC foundation. The protocol allows platform- point to connect to (from an unauthenticated list of endpoints independent and secure communication by design. The first provided by the server). version of OPC UA Unified Architecture was released in 2006, followed by four other releases up to the current specification B. Certificate Management in OPC UA 1.04 released in 2018. Eighteen parts constitute the protocol In order to establish a secure connection (Security Mode specification, each describing a feature of the protocol. Part 2 different from ‘None’), OPC UA applications (Clients and describes the security model of OPC UA, and Part 4 describes Servers) need to perform application authentication by ex- the services that implement security primitives. changing their Application Instance Certificates. Upon re- The standard details two communication strategies: a client- ceiving a certificate, an application needs to decide whether server model and a publisher-subscriber model. Both models the received application certificate is trustworthy and the allow messages to be signed to ensure authenticity or signed connection can be established or not. To this end, each OPC and encrypted to add confidentiality. OPC UA does not enforce UA application

Load more