OPC UA Invalid Server Nonces Vulnerability

OPC Foundation (OPCF) announced a Security Bulletin (CVE-2019-19135) on March 16, 2020, concerning a vulnerability in the OPC UA Java and .NET Stacks of OPC Foundation:

“… that could result in encrypted password credentials or signed X509 certificate credentials being sent in a form that can be intercepted and reused.”

Prosys OPC UA SDK for Java has the stack layer derived from the OPC Foundation Java Stack and is, therefore, affected by the same issue.

Details

The issue is related to some server applications not following the security specifications properly and reusing ServerNonces in communication. Servers built with Prosys OPC UA SDK for Java or Delphi or with any Unified Automation SDK are behaving properly and are not affected.

The suggested fix in the stack and SDK is to make the client applications check for vulnerability and reject connections with misbehaving servers.

The vulnerability concerns all communications that do not encrypt traffic, so in practice, security modes None and Sign are affected when user name or user certificate credentials are used. The fixed version of the client SDK for Java is disabling session activation (i.e., connections) if it identifies a misbehaving server. In this case, the connection is possible only without user credentials.

Prosys OPC UA Products Affected

The vulnerability affects directly:

  • All client applications built with Prosys OPC UA SDK for Java 4.2.0 and earlier
  • Prosys OPC UA Browser 4.0.2 and earlier
  • Prosys OPC UA Historian 1.0.0

Note that the vulnerability affects the applications only when connecting with misbehaving server applications using a user name or user certificate authentication.

Fixed Products

The issue is now fixed in Prosys OPC UA SDK 4.3.0, and Prosys OPC UA Browser 4.0.4, and we encourage everyone to update to these versions. Prosys OPC UA Historian will be updated later, respectively.

Fixing the issue with older library versions

Since the issue is related to security modes None and Sign only, when user name or user certificate-based authentication is used, you can avoid the issue by not using these modes in applications.

In general, if top-level security is a concern, SignAndEncrypt, with the most recent security policies, should be preferred.

More Security Information

You will find the currently announced security issues in Prosys OPC products from the blog under the #Security tag.

You might also like to read about the OPC UA Security Process of the OPC Foundation.

Author Info

Headshot of Jouni Aro

Jouni Aro

Chief Technology Officer

Email: jouni.aro@prosysopc.com

Related Posts

i-GuSystem – From MTConnect to OPC UA: Future-Proof CNC Data Collection with Forge

August 20, 2025 No Comments

i-GuSystem Ltd., a Finnish specialist in CNC program transfer and production data acquisition, adopted Prosys OPC UA Forge to extend its data integration from MTConnect into the OPC UA era, ensuring future-proof and scalable solutions. To meet the growing demand for OPC UA, i-GuSystem integrated Prosys OPC UA Forge as a future-proof layer. Forge enables direct OPC UA connectivity with output in XML, ensuring full compatibility with iguXMLsync and downstream systems like VisualFactory, MES, Azure cloud, and Power BI.
The first Forge deployment was completed in just two hours, delivering reliable results and proving the scalability of i-GuSystem’s solutions. By adopting Forge, i-GuSystem has seamlessly extended its CNC data expertise into the OPC UA era, future-proofing its architecture while continuing to provide rapid, hands-on results for its customers.

Read More »
Search Blogs with Key Words

Interested in this topic?

Get updated about new posts through our newsletter!
Subscribe to Our Newsletter