CyberRota Analysis
AI-GeneratedThe UserNameIdentityToken authentication handler in node-opcua versions prior to 2.166.0 is vulnerable due to improper verification of the session serverNonce, allowing an unauthenticated remote attacker to forge authentication tokens and potentially access accounts with empty passwords. Additionally, the lack of nonce binding enables replay attacks on captured tokens, further compromising session security. Organizations using affected versions of node-opcua should prioritize upgrading to version 2.166.0 to mitigate these risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.