CyberRota Analysis
AI-GeneratedNode-opcua clients, specifically those using the default keepSessionAlive setting, are vulnerable to a resource exhaustion issue due to improper handling of server clock skew, leading to repeated reconnection attempts and accumulation of file descriptors and memory. This can result in the client process or container being terminated when resources are depleted. Organizations utilizing node-opcua versions 2.0.0 to 2.170.0 should prioritize upgrading to version 2.170.0 to mitigate this high-severity vulnerability.
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. From 2.0.0 until 2.170.0, node-opcua clients using the default keepSessionAlive setting can enter a repeated reconnection cycle when an OPC UA server's clock skew causes BadInvalidTimestamp responses. ClientSessionKeepAliveManager._ping_server treated the server-originated ServiceFault as a network outage and forced a transport reconnect, while ClientTCP_transport._on_ACK_response used socket.end() after failed HEL/ACK negotiation and could leave the connection in FIN-WAIT-2 when the peer did not close. Repetition at the keepAliveInterval accumulates file descriptors and memory until the client process or container can be terminated by resource exhaustion. This issue is fixed in version 2.170.0.