p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости node-opcua

За последние 30 дней в node-opcua опубликовано уязвимостей: 0; в каталоге KEV: 0.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 6

  1. CVE-2026-68904

    Высокий · CVSS 7EPSS 0,44%Есть исправление

    node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion

    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 memor

    • Обновитесь до 2.170.0
    Опубликовано Обновлено
  2. CVE-2026-54156

    Высокий · CVSS 7.5EPSS 0,78%Есть исправление

    node-opcua: Unbounded nonce cache enables unauthenticated heap exhaustion DoS

    node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to 2.166.0, the process-global g_alreadyUsedNonce cache used by nonceAlreadyBeenUsed in packages/node-opcua-secure-channel/source/server/server_secure_channel_layer.ts records nonces from OpenSecureChannelRequest and CreateSession without expiration or a size limit. An unauthenticated remote attacker can repeatedly create sessions with unique nonces, causing entries to persist after session expiry and accumulate across connection cycles even when maxSessions=10 limits concurrent sessions. The resulting unbounded heap growth can exhaust the default Node.js heap and crash

    • Обновитесь до 2.166.0
    Опубликовано Обновлено
  3. CVE-2026-54155

    Высокий · CVSS 7.7EPSS 0,42%Нет опубликованного исправления

    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 sessi

    Опубликовано Обновлено
  4. CVE-2022-24375

    Высокий · CVSS 7.5EPSS 1,67%Есть исправление

    Denial of Service (DoS)

    The package node-opcua before 2.74.0 are vulnerable to Denial of Service (DoS) when bypassing the limitations for excessive memory consumption by sending multiple CloseSession requests with the deleteSubscription parameter equal to False.

    • Обновитесь до 2.74.0
    Опубликовано Обновлено
  5. CVE-2022-21208

    Высокий · CVSS 7.5EPSS 1,46%Есть исправление

    Denial of Service (DoS)

    The package node-opcua before 2.74.0 are vulnerable to Denial of Service (DoS) due to a missing limitation on the number of received chunks - per single session or in total for all concurrent sessions. An attacker can exploit this vulnerability by sending an unlimited number of huge chunks (e.g. 2GB each) without sending the Final closing chunk.

    • Обновитесь до 2.74.0
    Опубликовано Обновлено
  6. CVE-2022-25231

    Высокий · CVSS 7.5EPSS 1,32%Есть исправление

    Denial of Service (DoS)

    The package node-opcua before 2.74.0 are vulnerable to Denial of Service (DoS) by sending a specifically crafted OPC UA message with a special OPC UA NodeID, when the requested memory allocation exceeds the v8’s memory limit.

    • Обновитесь до 2.74.0
    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →