CVE-2019-19135: Insufficient Nonce Validation in Eclipse Milo Client

org.eclipse.milo:sdk-client Updated 02 Oct 2025

Summary

16/03/2020
Yes i
High
7.4

CVE-2019-19135: Insufficient Nonce Validation in Eclipse Milo Client. Affects org.eclipse.milo:sdk-client versions < 0.3.6. Fixed in 0.3.6. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Eclipse Milo Client is a software development kit (SDK) that provides a Java implementation of the OPC Unified Architecture (UA) protocol. It allows developers to create OPC UA clients to interact with OPC UA servers. OPC UA is a machine-to-machine communication protocol for industrial automation. The Milo Client supports various security features, including authentication and encryption.

The vulnerability identified as CVE-2019-19135 affects the Milo Client when certain conditions are met. Specifically, when the SecurityPolicy is set to None and the server has a defect causing it to send null, empty, or zeroed nonces, a credential replay attack can occur. This vulnerability can lead to unauthorized access and compromise of sensitive information.

Vulnerability Detail

The vulnerability arises due to insufficient nonce validation in the Eclipse Milo Client. Nonces are random numbers used to prevent replay attacks. In this case, when the SecurityPolicy is set to None, and the server sends null, empty, or zeroed nonces, the client fails to properly validate them. This allows an attacker to replay credentials and gain unauthorized access to the server.

To exploit this vulnerability, the following conditions must be met:

  • SecurityPolicy is set to None
  • Username/password or X509-based authentication is used
  • The server has a defect causing it to send null, empty, or zeroed nonces.

The impact of this vulnerability is credential replay, which can lead to unauthorized access and compromise of sensitive information.

How To Fix

Latest published version: 0.6.16 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.3.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating the Eclipse Milo Client is not immediately feasible, a workaround is to avoid using username/password or X509-based authentication with a SecurityPolicy of None. Instead, consider using a different security policy or upgrading to a more recent version of the Milo Client that implements the relaxed treatment of validation.

Conclusion

The vulnerability identified as CVE-2019-19135 in the Eclipse Milo Client can lead to credential replay attacks, potentially resulting in unauthorized access and compromise of sensitive information. It is crucial to update the Milo Client to version 0.3.6 or later to mitigate this vulnerability. If immediate updating is not possible, consider using alternative authentication methods or upgrading to a version that implements the relaxed treatment of validation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.eclipse.milo:sdk-client →

Share this vulnerability

FAQ

The Eclipse Milo Client is a Java SDK that allows developers to create OPC UA clients for interacting with OPC UA servers in industrial automation.

OPC UA (Unified Architecture) is a machine-to-machine communication protocol for industrial automation. It provides a standardized way for different systems to exchange data and information.

A nonce is a random number used to prevent replay attacks. It is included in the communication between a client and a server to ensure the freshness and integrity of the data.

A credential replay attack is a type of attack where an attacker intercepts and replays previously captured credentials to gain unauthorized access to a system or service.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software, using just the pom.xml file without requiring access to the code or installation.

How To Fix

Latest published version: 0.6.16 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.3.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback