5 matches found
@frangoteam/fuxa (>=1.1.7, <=1.1.8), @hive-command/discovery-server (>=1.3.2-alpha.86, <=1.3.3-alpha.35) +19 more potentially affected by CVE-2022-25231 via node-opcua (>=2.1.9, <=2.73.1)
node-opcua NPM version =2.1.9, =1.1.7, =1.3.2-alpha.86, =1.3.6-alpha.36, =1.3.5, =0.0.3, =0.0.3, =0.0.2, =1.3.0-alpha.0, =0.8.0, =2.10.0, =2.10.0, =4.0.0, =1.0.0, =0.2.93, =0.2.286 and more Source cves: CVE-2022-25231 Source advisory: OSV:GHSA-QPGC-XH7J-52Q8...
CVE-2022-25231
CVE-2022-25231 affects node-opcua before 2.74.0. A crafted OPC UA message with a specific NodeID can trigger memory-allocation-induced DoS when v8 memory limits are exceeded, impacting availability. Mitigation: upgrade to node-opcua 2.74.0 or later (remediation consistently recommended across OSV...
CVE-2022-25231 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...
CVE-2022-25231 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...
@frangoteam/fuxa (>=1.1.7, <=1.1.8), @hive-command/discovery-server (>=1.3.2-alpha.86, <=1.3.3-alpha.35) +19 more potentially affected by CVE-2022-25231 via node-opcua (>=2.1.9, <=2.73.1)
node-opcua NPM version =2.1.9, =1.1.7, =1.3.2-alpha.86, =1.3.6-alpha.36, =1.3.5, =0.0.3, =0.0.3, =0.0.2, =1.3.0-alpha.0, =0.8.0, =2.10.0, =2.10.0, =4.0.0, =1.0.0, =0.2.93, =0.2.286 and more Source cves: CVE-2022-25231 Source advisory: SNYK:JS-NODEOPCUA-2988724...