Node-opcua
node-opcua: Missing nonce verification in UserNameIdentityToken authentication
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to 2.166.0, the UserNameIdentityToken authentication handler in packages/node-opcua-server/source/opcua_server.ts decrypts an RSA-OAEP password blob but does not verify that the trailing bytes match the current session serverNonce. An unauthenticated remote attacker can obtain the server public key through GetEndpoints and forge a blob whose little-endian length produces an empty password passed to isValidUser, compromising accounts that accept an empty password. Missing nonce binding also allows a captured UserNameIdentityToken ciphertext to be replayed in another session, and SecurityMode=None removes the separate client-signature safeguard. This issue is fixed in version 2.166.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.166.0
Fixed in 2.166.0
Mitigation
Upgrade node-opcua to 2.166.0 or later.
References
- Vendor advisory github.com/node-opcua/node-opcua/security/advi…
- Patch github.com/node-opcua/node-opcua/commit/c6b057…
- Release notes github.com/node-opcua/node-opcua/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.