What is CVE-2019-19135?

CVE-2019-19135 is a high-severity use of insufficiently random values vulnerability in org.eclipse.milo:sdk-client (maven), affecting versions <= 0.3.4. It is fixed in 0.3.6. Security-sensitive operations rely on values that are predictable or insufficiently random.

How severe is CVE-2019-19135?

CVE-2019-19135 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.eclipse.milo:sdk-client are affected by CVE-2019-19135?

org.eclipse.milo:sdk-client (maven) versions <= 0.3.4 is affected.

Is there a fix for CVE-2019-19135?

Yes. CVE-2019-19135 is fixed in 0.3.6. Upgrade to this version or later.

Is CVE-2019-19135 exploitable, and should I be worried?

Whether CVE-2019-19135 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-19135 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2019-19135?

Upgrade org.eclipse.milo:sdk-client to 0.3.6 or later.

CVE-2019-19135 in org.eclipse.milo:sdk-client

Q: How severe is CVE-2019-19135?

CVE-2019-19135 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.eclipse.milo:sdk-client are affected by CVE-2019-19135?

org.eclipse.milo:sdk-client (maven) versions <= 0.3.4 is affected.

Q: Is there a fix for CVE-2019-19135?

Yes. CVE-2019-19135 is fixed in 0.3.6. Upgrade to this version or later.

Q: Is CVE-2019-19135 exploitable, and should I be worried?

Whether CVE-2019-19135 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-19135 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-19135?

Upgrade org.eclipse.milo:sdk-client to 0.3.6 or later.

Summary

Insufficient Nonce Validation in Eclipse Milo Client

Workarounds

Do not use username/password or X509-based authentication with SecurityPolicy of None.

References

https://opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2019-19135.pdf

For more information

If you have any questions or comments about this advisory:

Open an issue at https://github.com/eclipse/milo/issues
Email the mailing list

Impact

Credential replay affecting those connected to a server when all 3 of the following conditions are met:

SecurityPolicy is None
using username/password or X509-based authentication
the server has a defect causing it to send null/empty or zeroed nonces

Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.

CVE-2019-19135 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.3.6); upgrading removes the vulnerable code path.

Affected versions

org.eclipse.milo:sdk-client (<= 0.3.4)

Security releases

org.eclipse.milo:sdk-client → 0.3.6 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem has been patched in version 0.3.6. A more relaxed treatment of validation as agreed upon by the OPC UA Security Working Group is implemented in version 0.3.7.

Frequently Asked Questions

What is CVE-2019-19135? CVE-2019-19135 is a high-severity use of insufficiently random values vulnerability in org.eclipse.milo:sdk-client (maven), affecting versions <= 0.3.4. It is fixed in 0.3.6. Security-sensitive operations rely on values that are predictable or insufficiently random.
How severe is CVE-2019-19135? CVE-2019-19135 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.eclipse.milo:sdk-client are affected by CVE-2019-19135? org.eclipse.milo:sdk-client (maven) versions <= 0.3.4 is affected.
Is there a fix for CVE-2019-19135? Yes. CVE-2019-19135 is fixed in 0.3.6. Upgrade to this version or later.
Is CVE-2019-19135 exploitable, and should I be worried? Whether CVE-2019-19135 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-19135 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-19135? Upgrade org.eclipse.milo:sdk-client to 0.3.6 or later.