Skip to content

Insufficient Nonce Validation in Eclipse Milo Client

High severity GitHub Reviewed Published Mar 16, 2020 in eclipse-milo/milo • Updated Feb 1, 2023

Package

maven org.eclipse.milo:sdk-client (Maven)

Affected versions

<= 0.3.4

Patched versions

0.3.6

Description

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

Patches

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.

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:

References

@eclipsewebmaster eclipsewebmaster published to eclipse-milo/milo Mar 16, 2020
Published by the National Vulnerability Database Mar 16, 2020
Reviewed Mar 16, 2020
Published to the GitHub Advisory Database Mar 16, 2020
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.128%
(49th percentile)

Weaknesses

CVE ID

CVE-2019-19135

GHSA ID

GHSA-pq4w-qm9g-qx68

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.