Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation via Mojo. If the endpoint's task runner does not match the current task runner (or an equivalent main-thread task runner for the ChannelProxy) when executing a message dispatch task for that endpoint, it dispatches it on the wrong sequence.
Remediation
Upgrade electron to version 13.6.8, 14.2.4, 15.3.5 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds via the V8 component in Chrome.
Remediation
Upgrade electron to version 11.4.4, 10.4.4, 12.0.6 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write via ANGLE in Chrome.
Remediation
Upgrade electron to version 12.0.13, 11.4.10 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion via the V8 module in Chromium.
Remediation
Upgrade electron to version 14.2.1, 13.6.2, 12.2.3 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8 Turbofan, exploiting this vulnerability is possible via a crafted HTML page.
Remediation
Upgrade electron to version 15.5.3, 16.2.4, 17.4.2 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. An unknown vunerability exists in Chrome.
Remediation
Upgrade electron to version 9.4.1, 10.3.2 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via handling of cookies.
Remediation
Upgrade electron to version 9.4.2, 10.3.1, 11.2.2 or higher.
References
critical severity
- Vulnerable module: socket.io-parser
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1
Overview
socket.io-parser is a socket.io protocol parser
Affected versions of this package are vulnerable to Improper Input Validation.
when parsing attachments containing untrusted user input. Attackers can overwrite the _placeholder object to place references to functions in query objects.
PoC
const decoder = new Decoder();
decoder.on("decoded", (packet) => {
console.log(packet.data); // prints [ 'hello', [Function: splice] ]
})
decoder.add('51-["hello",{"_placeholder":true,"num":"splice"}]');
decoder.add(Buffer.from("world"));
Remediation
Upgrade socket.io-parser to version 3.3.3, 3.4.2, 4.0.5, 4.2.1 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion due to a flaw in the WebAssembly component. An attacker can execute arbitrary code on the victim's machine by convincing them to visit a maliciously crafted HTML page.
Remediation
Upgrade electron to version 27.3.9, 28.2.10, 29.2.0 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Mojo interface. An attacker can potentially exploit heap corruption by delivering a crafted HTML page.
Remediation
Upgrade electron to version 27.3.3 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to improper handling of objects in memory in the ANGLE graphics engine. An attacker can cause heap corruption and potentially execute arbitrary code by convincing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 27.3.9, 28.2.10, 29.2.0 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@37.2.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') via the lack of limitation on max inlining ids in MaglevGraphBuilder. An attacker can achieve heap corruption and potentially execute arbitrary code by enticing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 37.2.5 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read via a crafted HTML page. An attacker can potentially perform a sandbox escape by manipulating the memory outside its intended buffer limits.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion via crafted HTML content. This can be exploited to escape the v8 sandbox and execute arbitrary code on the operating system.
Remediation
Upgrade electron to version 31.7.1, 32.2.1 or higher.
References
critical severity
- Vulnerable module: form-data
- Introduced through: snappy-core@github:snappyrobotics/snappy-core, electron@1.8.8 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › ascii-art@1.5.1 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8 › electron-download@3.3.0 › nugget@2.2.0 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-feedparser@0.1.16 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-twitter@0.1.15 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › request@2.88.2 › form-data@2.3.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › form-data@2.1.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › form-data@0.2.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › form-data@1.0.1
Overview
Affected versions of this package are vulnerable to Predictable Value Range from Previous Values via the boundary value, which uses Math.random(). An attacker can manipulate HTTP request boundaries by exploiting predictable values, potentially leading to HTTP parameter pollution.
Remediation
Upgrade form-data to version 2.5.4, 3.0.4, 4.0.4 or higher.
References
critical severity
- Vulnerable module: hawk
- Introduced through: serialport@4.0.7, unirest@0.5.1 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
Overview
hawk is a library for the HTTP Hawk Authentication Scheme.
Affected versions of this package are vulnerable to Authentication Bypass. The incoming (client supplied) hash of the payload is trusted by the server and not verified before the signature is calculated.
A malicious actor in the middle can alter the payload and the server side will not identify the modification occurred because it simply uses the client provided value instead of verify the hash provided against the modified payload.
According to the maintainers this issue is to be considered out of scope as "payload hash validation is optional and up to developer to implement".
Remediation
There is no fixed version for hawk.
References
critical severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds Write via the V8 engine. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion'). Type confusion in V8 in Google Chrome allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 12.0.12, 11.4.9 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access Restriction Bypass in Blink.
Remediation
Upgrade electron to version 13.5.0, 12.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap Buffer Overflow via WebAudio.
Remediation
Upgrade electron to version 11.4.0, 10.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap Overflow. A Heap buffer overflow exists in the media component of Google Chrome, which also affects chromium.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow. A heap buffer overflow flaw was found in the UI component of the Chromium browser.
Remediation
Upgrade electron to version 9.4.0, 10.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow via the WebRTC module in Chromium.
Remediation
Upgrade electron to version 14.2.0, 13.5.2, 12.2.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the ANGLE component.
Remediation
Upgrade electron to version 26.6.5, 27.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow via a crafted HTML page. An attacker can potentially exploit heap corruption by deceiving a user to visit a malicious web page.
Remediation
Upgrade electron to version 27.3.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the ANGLE component. An attacker can potentially exploit heap corruption through a crafted HTML page.
Remediation
Upgrade electron to version 27.3.11, 28.3.1, 29.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow through the WebRTC component. An attacker can cause heap corruption and potentially execute arbitrary code by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.3, 30.1.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Access Control. An insufficient policy enforcement flaw was found in the networking component of chromium.
Remediation
Upgrade electron to version 9.4.0, 10.1.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Access Control. It has an inappropriate implementation in V8.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Access Control due to an inappropriate implementation in Extensions. An attacker can bypass site isolation.
Remediation
Upgrade electron to version 31.7.4, 32.2.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation. An insufficient data validation flaw was found in the WASM component of the Chromium browser.
Remediation
Upgrade electron to version 9.4.0, 10.1.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.3.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Restriction of Operations within the Bounds of a Memory Buffer due to an inappropriate implementation in the V8 engine. An attacker can potentially perform out of bounds memory access by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.3.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Integer Overflow or Wraparound via the Mojo component of chromium.
Remediation
Upgrade electron to version 10.4.4, 12.0.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Integer Overflow or Wraparound due to handle reuse in Mojo.
Remediation
Upgrade electron to version 14.2.7, 15.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Interger Underflow in ANGLE. A remote attacker could potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 14.2.5, 15.3.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds. Object lifecycle issue in audio.
Remediation
Upgrade electron to version 11.4.0, 10.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read allowing a remote attacker to exploit heap corruption via a crafted HTML page.
Note: The Stable channel has been updated to 120.0.6099.234 for Mac devices.
Remediation
Upgrade electron to version 26.6.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read through the V8 engine. An attacker can access memory locations outside of the intended boundary by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read via a crafted HTML page. An attacker can access memory locations outside the intended boundary by crafting a malicious HTML page that triggers the flaw.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write via a data race in the audio component. A remote attacker could potentially exploit heap corruption using a crafted HTML page.
Remediation
Upgrade electron to version 10.4.1, 11.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds Write through the Streams API. An attacker can execute arbitrary code within a sandboxed environment by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Privilege Context Switching Error in libuv's handling of io_uring operations called before calling setuid(). This allows users to elevate privileges.
PoC
const { spawn } = require('node:child_process');
const process = require('process');
process.env['UV_USE_IO_URING']=1;
process.setuid(400);
const ls = spawn('cmd.exe', [' whoami']);
ls.stdout.on('data', (data) => {
console.log(`stdout: ${data}`);
});
ls.stderr.on('data', (data) => {
console.error(`stderr: ${data}`);
});
ls.on('close', (code) => {
console.log(`child process exited with code ${code}`);
});
console.log("The user identity of the Node.js" + " process:", process.getuid());
Remediation
Upgrade electron to version 29.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8 via Chrome.
Remediation
Upgrade electron to version 12.0.16, 11.4.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion via Blink layout in Chrome.
Remediation
Upgrade electron to version 13.5.0, 12.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8. This allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 13.6.3, 14.2.2, 15.3.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in loader in Google Chrome. This can lead to heap corruption which is exploited through a crafted HTML page.
Remediation
Upgrade electron to version 13.6.6, 14.2.4, 15.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8 in Google Chrome allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 13.6.8, 14.2.5, 15.3.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@17.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8.
Remediation
Upgrade electron to version 17.4.11, 18.3.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8.
Remediation
Upgrade electron to version 19.1.5, 20.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@7.3.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8.
Remediation
Upgrade electron to version 7.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion due to the V8 process. An attacker can potentially perform arbitrary read/write by exploiting a crafted HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@8.5.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the site isolation.
Remediation
Upgrade electron to version 8.5.4, 9.3.5, 10.1.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. A use after free flaw was found in the PPAPI component of the Chromium browser.
Remediation
Upgrade electron to version 9.4.0, 10.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Media.
Remediation
Upgrade electron to version 11.2.1, 9.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. It hands sub-queries with both a correlated WHERE clause and a HAVING 0 clause where the parent query is itself an aggregate.
Remediation
Upgrade electron to version 11.2.1, 9.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. When a LayoutInline is removed, LineBoxList::DirtyLinesFromChangedChild tries to mark affected
RootInlineBox dirty.
When the |LayoutInline| to be removed is culled, it tries to find the RootInlineBox from its previous siblings, then look for its previous and next RootInlineBoxes.
Occasionally, the next next line of the previous sibling is wrapped at the LayoutInline, and that its LineBreakObj() holds the reference to the LayoutInline. This patch marks such RootInlineBox dirty.
Remediation
Upgrade electron to version 11.4.0, 10.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. It allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 10.4.2, 11.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via a vulnerability that exists in Blink in Chromium. A remote attacker can trick the victim to visit a specially crafted web page, trigger a use-after-free error and execute arbitrary code on the system.
Remediation
Upgrade electron to version 11.4.4, 10.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via Chrome which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 12.0.5, 11.4.4, 10.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via chromium which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 12.0.5, 11.4.4, 10.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via Aura in Google Chrome which allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 12.0.5, 11.4.4, 10.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Navigation component of chromium.
Remediation
Upgrade electron to version 10.4.4, 11.4.4, 12.0.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in the chromium extensions resource.
Remediation
Upgrade electron to version 11.4.4, 10.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in File API.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Notifications.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. Use after free in Loader in Google Chrome allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 12.0.12, 11.4.9 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in BFCache in Google Chrome, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 12.0.13, 11.4.9 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebGL.
Remediation
Upgrade electron to version 12.0.13, 11.4.10 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebRTC.
Remediation
Upgrade electron to version 12.0.14, 11.4.10 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebAudio.
Remediation
Upgrade electron to version 12.0.14, 11.4.10 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Blink XSLT.
Remediation
Upgrade electron to version 12.0.16, 11.4.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebSerial via Chrome.
Remediation
Upgrade electron to version 12.0.16, 11.4.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in V8 via Chrome.
Remediation
Upgrade electron to version 12.0.16, 11.4.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in GPU.
Remediation
Upgrade electron to version 13.1.8, 12.0.16, 11.4.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Autofill.
Remediation
Upgrade electron to version 12.0.16, 11.4.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Indexed DB API.
Remediation
Upgrade electron to version 13.5.0, 12.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@2.0.18.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Chromium FileReader.
Note: This vulnerability affects all software based on Chromium, including Electron.
Remediation
Upgrade electron to version 2.0.18, 3.0.16, 3.1.6, 4.0.8 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via heap corruption through a crafted HTML page.
Remediation
Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in the file system API, through a heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Garbage Collection module in Chromium.
Remediation
Upgrade electron to version 14.2.1, 13.6.2, 12.2.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Web Transport module in Chromium.
Remediation
Upgrade electron to version 14.2.1, 13.6.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in loader in Google Chrome. This allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 13.6.3, 14.2.2, 15.3.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.0.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in the storage foundation, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page
Remediation
Upgrade electron to version 16.0.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.3.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in media in Google Chrome which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 15.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via file API in Google Chrome prior to 96.0.4664.93. It allows a remote attacker who have compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 13.6.6, 14.2.4, 15.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free on context loss.
Remediation
Upgrade electron to version 14.2.7, 15.4.0, 16.0.10 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free when the source framebuffer's extents were accidentally used instead of the blit area extents.
Remediation
Upgrade electron to version 14.2.7, 15.4.0, 16.0.10 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in the BFCache, due to the attempts to cache an interstitial which results in a crash.
Remediation
Upgrade electron to version 16.2.4, 17.4.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in regular expressions (V8).
Remediation
Upgrade electron to version 15.5.3, 16.2.4, 17.4.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Angle, when pausing XFB then deleting a buffer.
Remediation
Upgrade electron to version 15.5.4, 16.2.6, 17.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Vulkan.
Remediation
Upgrade electron to version 15.5.6, 16.2.6, 17.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.2.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in File System API.
Remediation
Upgrade electron to version 16.2.6, 17.4.3, 18.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in SwiftShader.
Remediation
Upgrade electron to version 15.5.4, 16.2.5, 17.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to improper cache state validation after the XFB buffer was deleted.
Remediation
Upgrade electron to version 15.5.6, 16.2.7, 17.4.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@17.4.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Angle.
Remediation
Upgrade electron to version 17.4.8, 18.3.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free when glBufferData redefines a buffer and the new buffer is smaller than the old buffer.
Remediation
Upgrade electron to version 18.3.11, 19.0.15 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Blink, when a DisplayLock is unlocked via ForceUnlockIfNeeded.
Remediation
Upgrade electron to version 18.3.11 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.0.15.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in SwiftShader.
Remediation
Upgrade electron to version 19.0.15 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.14.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebSQL
Remediation
Upgrade electron to version 18.3.14, 20.1.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.12.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebSQL.
Remediation
Upgrade electron to version 18.3.12, 19.0.16, 20.1.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.14.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Layout.
Remediation
Upgrade electron to version 19.1.0, 18.3.14 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.12.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Network Service
Remediation
Upgrade electron to version 20.1.2, 19.1.0, 18.3.12 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.14.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Frames, via a crafted HTML page.
Remediation
Upgrade electron to version 18.3.14, 19.1.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Layout.
Remediation
Upgrade electron to version 19.1.5, 20.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebCodecs, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 19.1.7, 20.3.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Web Workers, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 19.1.7, 20.3.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@20.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Mojo, via heap corruption.
Remediation
Upgrade electron to version 20.3.9, 21.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@20.3.12.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebRTC, causing heap corruption.
Remediation
Upgrade electron to version 20.3.12, 21.4.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. Multiple user after free vulnerabilities exists in the WebAudio component of chromium.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. It allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the audio component. It allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@7.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the audio component.
Remediation
Upgrade electron to version 8.2.1, 7.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. It allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@8.3.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in WebRTC.
Remediation
Upgrade electron to version 8.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the WebAudio component. An attacker can potentially exploit heap corruption by convincing a user to visit a crafted HTML page.
Remediation
Upgrade electron to version 26.6.5, 27.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Web Audio feature. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 26.6.8, 27.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to the improper handling of objects in memory in the Dawn component. An attacker can potentially exploit heap corruption through a crafted HTML page.
Remediation
Upgrade electron to version 27.3.9, 28.2.10, 29.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to improper handling in the WebCodecs component. An attacker can achieve arbitrary read/write access by crafting a malicious HTML page.
Remediation
Upgrade electron to version 27.3.9, 28.2.10, 29.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to improper handling of objects in memory in the Dawn component. An attacker can cause heap corruption and potentially execute arbitrary code by convincing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 27.3.11, 28.3.1, 29.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Media Session process. An attacker can execute arbitrary code inside a sandbox by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Dawn process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Dawn component. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in the scheduling process. An attacker can execute arbitrary code inside a sandbox by using a crafted HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to the improper handling of memory in the Dawn process. An attacker can cause heap corruption by crafting a malicious HTML page.
Note: 126.0.6478.56 is the fixed version for Windows and Mac. Version 126.0.6478.54 fixes the vulnerability in Linux
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Dawn process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Note: 126.0.6478.56 is the fixed version for Windows and Mac. Version 126.0.6478.54 fixes the vulnerability in Linux
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: cross-spawn
- Introduced through: nodemon@1.19.4
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › update-notifier@2.5.0 › boxen@1.3.0 › term-size@1.2.0 › execa@0.7.0 › cross-spawn@5.1.0Remediation: Upgrade to nodemon@2.0.3.
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.
PoC
const { argument } = require('cross-spawn/lib/util/escape');
var str = "";
for (var i = 0; i < 1000000; i++) {
str += "\\";
}
str += "◎";
console.log("start")
argument(str)
console.log("end")
// run `npm install cross-spawn` and `node attack.js`
// then the program will stuck forever with high CPU usage
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade cross-spawn to version 6.0.6, 7.0.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@33.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') in v8.
Remediation
Upgrade electron to version 33.4.6, 34.3.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to External Control of Assumed-Immutable Web Parameter via a crafted HTML page. An attacker can perform an out of bounds memory write by sending a specially crafted HTML content.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Skia
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Skia.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Skia.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@37.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Incorrect Calculation of Buffer Size via insufficient validation of untrusted input in ANGLE and GPU. An attacker can escape the sandbox by submitting a specially crafted HTML page.
Remediation
Upgrade electron to version 37.2.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write via a crafted HTML page. An attacker can execute arbitrary code inside a sandbox by crafting a malicious HTML page.
Remediation
Upgrade electron to version 31.7.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.3.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write through a crafted HTML page. An attacker can execute arbitrary code inside a sandbox by crafting malicious HTML content.
Remediation
Upgrade electron to version 32.3.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.3.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write via a crafted HTML page. An attacker can potentially exploit heap corruption by sending a specially crafted HTML page to the victim.
Remediation
Upgrade electron to version 32.3.2, 33.4.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.3.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write through crafted HTML pages. An attacker can exploit heap corruption by sending a specially crafted HTML page to the victim.
Remediation
Upgrade electron to version 32.3.2, 33.4.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.3.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in v8 engine.
Remediation
Upgrade electron to version 32.3.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@37.2.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via MediaStreamTrackImpl. An attacker can cause heap corruption by enticing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 37.2.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Dawn component.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Swiftshader process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.5, 30.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Dawn process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.5, 30.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free due to the improper handling of memory in the Dawn component. An attacker can cause heap corruption and potentially execute arbitrary code by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.5, 30.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Dawn component. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.5, 30.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@30.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Dawn component. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 30.4.0, 31.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@30.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Loader component. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 30.4.0, 31.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Dawn component. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the WebAudio process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Serial process. An attacker can potentially exploit heap corruption.
Remediation
Upgrade electron to version 31.7.5, 32.2.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Compositing process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 31.7.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@33.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the V8 engine. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 33.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.3.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the V8 engine.
Remediation
Upgrade electron to version 32.3.3, 33.4.3 or higher.
References
high severity
- Vulnerable module: socket.io
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1
Overview
socket.io is a node.js realtime framework server.
Affected versions of this package are vulnerable to Uncaught Exception in handling error events. If there is no listener set up for such events, an attacker can send packets containing them to crash the Node process.
Workaround
This vulnerability can be avoided by attaching a listener for error events, such as
io.on("connection", (socket) => {
socket.on("error", () => {
// ...
});
});
Remediation
Upgrade socket.io to version 2.5.1, 4.6.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@37.2.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') via lack of support for escapes in PreParserIdentifier V8` process. An attacker can achieve heap corruption by enticing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 37.2.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@17.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the WebRTC component.
Remediation
Upgrade electron to version 17.4.11, 18.3.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow through the V8 engine. An attacker can corrupt memory and potentially execute arbitrary code by crafting a malicious HTML page.
Note: This is only exploitable if the user navigates to or is redirected to a malicious web page.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation. It allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Remediation
Upgrade electron to version 10.4.2, 11.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds. Out of bounds memory access in V8 in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. This vulnerability relates to an electron component.
Remediation
Upgrade electron to version 10.4.2, 11.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@22.3.23.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds when the V8 engine processes a carefully crafted HTML page. An attacker can perform an out of bounds memory read, thereby potentially gaining unauthorized access to sensitive information.
Remediation
Upgrade electron to version 22.3.23, 24.8.2, 25.8.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds memory access in V8 component. This vulnerability allowed a remote attacker to perform arbitrary read/write via a crafted HTML page.
Remediation
Upgrade electron to version 27.3.10, 28.3.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read through the V8 engine. An attacker can access memory locations outside of the intended bounds by crafting a malicious HTML page.
Note: This is only exploitable if the user navigates to or is redirected to a malicious web page.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Note: The Stable channel has been updated to 120.0.6099.234 for Mac devices.
Remediation
Upgrade electron to version 26.6.6, 27.2.3, 28.1.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write in Dawn.
Remediation
Upgrade electron to version 31.7.4, 32.2.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in InferHasInPrototypeChain of the V8 engine.
Remediation
Upgrade electron to version 31.7.1, 32.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion via the V8 engine.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@37.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via improper handling of possible socket destruction in P2PSocketTcpBase. An attacker can achieve heap corruption and potentially execute arbitrary code by enticing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 37.2.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Mojo runtime libraries collection. This allows an attacker to exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 27.3.4, 28.2.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Audio process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Navigation process. An attacker can exploit heap corruption by convincing a user to install a malicious extension.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via specific UI gestures in the Screen Capture feature. An attacker can potentially exploit heap corruption by convincing a user to visit a crafted HTML page.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free through the Media Stream process. An attacker can potentially exploit heap corruption by convincing a user to perform specific UI gestures on a crafted HTML page.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
high severity
- Vulnerable module: node-red
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2
Overview
node-red is a visual tool for wiring the Internet of Things.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks.
Details
<
Remediation
Upgrade node-red to version 0.18.6 or higher.
References
high severity
- Vulnerable module: nodemailer
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › nodemailer@1.11.0
Overview
nodemailer is an Easy as cake e-mail sending from your Node.js applications
Affected versions of this package are vulnerable to Command Injection. Use of crafted recipient email addresses may result in arbitrary command flag injection in sendmail transport for sending mails.
PoC
-bi@example.com (-bi Initialize the alias database.)
-d0.1a@example.com (The option -d0.1 prints the version of sendmail and the options it was compiled with.)
-Dfilename@example.com (Debug output ffile)
Remediation
Upgrade nodemailer to version 6.4.16 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@23.2.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Access Control via nested unserializable return value when using contextIsolation and contextBridge are affected.
Exploiting this vulnerability allows code running in the main world context in the renderer to reach into the isolated Electron context and perform privileged actions.
Note
This issue is exploitable under either of two conditions:
If an API exposed to the main world via
contextBridgecan return an object or array that contains a JS object that cannot be serialized, such as a canvas rendering context. This would normally result in anError: object could not be clonedexception being thrown.If an API exposed to the main world via
contextBridgehas a return value that throws a user-generated exception while being sent over the bridge, such as a dynamic getter property on an object that throws an error when being computed.
Workaround
The app-side workaround is to ensure that such a case, as mentioned in the workaround section, is not possible.
Ensure all values returned from a function exposed over the context bridge are supported and that any objects returned from functions do not have dynamic getters that can throw exceptions.
Auditing your exposed API is likely to be quite difficult, so we strongly recommend you update to a patched version of Electron.
Remediation
Upgrade electron to version 23.2.3, 25.0.0-alpha.2 or higher.
References
high severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both \ and / characters as path separators. However, \ is a valid filename character on posix systems.
By first creating a directory, and then replacing that directory with a symlink, it is possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location. This can lead to extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at FOO, followed by a symbolic link named foo, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but not from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the FOO directory would then be placed in the target of the symbolic link, thinking that the directory had already been created.
Remediation
Upgrade tar to version 6.1.7, 5.0.8, 4.4.16 or higher.
References
high severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic is insufficient when extracting tar files that contain two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts.
A specially crafted tar archive can include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. This leads to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and extracting arbitrary files into that location.
Remediation
Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.
References
high severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain .. path portions, and resolving the sanitized paths against the extraction target directory.
This logic is insufficient on Windows systems when extracting tar files that contain a path that is not an absolute path, but specify a drive letter different from the extraction target, such as C:some\path. If the drive letter does not match the extraction target, for example D:\extraction\dir, then the result of path.resolve(extractionDirectory, entryPath) resolves against the current working directory on the C: drive, rather than the extraction target directory.
Additionally, a .. portion of the path can occur immediately after the drive letter, such as C:../foo, and is not properly sanitized by the logic that checks for .. within the normalized and split portions of the path.
Note: This only affects users of node-tar on Windows systems.
Remediation
Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.
References
high severity
- Vulnerable module: body-parser
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › body-parser@1.15.2
Overview
Affected versions of this package are vulnerable to Asymmetric Resource Consumption (Amplification) via the extendedparser and urlencoded functions when the URL encoding process is enabled. An attacker can flood the server with a large number of specially crafted requests.
Remediation
Upgrade body-parser to version 1.20.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@2.0.17.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Arbitrary Code Execution.
Opening a BrowserView with sandbox: true or nativeWindowOpen: true and nodeIntegration: false results in a webContents where window.open() can be called and the newly opened child will have nodeIntegration enabled.
Remediation
Upgrade electron to version 2.0.17, 3.0.15, 3.1.3, 4.0.4, 5.0.0-beta.2 or higher.
If for some reason you are unable to upgrade your Electron version, you can mitigate this issue by disabling all child web contents: view.webContents.on('-add-new-contents', e => e.preventDefault());
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@22.3.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read in GPU Video in Google Chrome prior to 111.0.5563.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 22.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@7.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Site Isolation Bypass. parent_execution_origin_ is provided from parent's RenderFrameHostImpl::last_committed_origin_ that is set during navigation commit. Worker creation IPC from the renderer to browser could race with navigation commit, and could see the wrong last committed origin.
Remediation
Upgrade electron to version 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. Since JavaScript may detach the underlying buffers, they need to be checked to ensure they're still valid before using them for decoding.
Remediation
Upgrade electron to version 10.2.0, 9.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. An AudioContext is considered to have activity if it's not closed. Previously, suspended contexts were considered has having no activity, but that's not quite true since the context can be resumed at any time after. This would allow contexts to be collected prematurely even though the context was resumed. This causes the audio thread to access objects that are possibly deleted.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.0.0-beta.6 or higher.
References
high severity
new
- Vulnerable module: nodemailer
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › nodemailer@1.11.0
Overview
nodemailer is an Easy as cake e-mail sending from your Node.js applications
Affected versions of this package are vulnerable to Uncontrolled Recursion in the addressparser function. An attacker can cause the process to terminate immediately by sending an email address header containing deeply nested groups, separated by many :s.
Remediation
Upgrade nodemailer to version 7.0.11 or higher.
References
high severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Overwrite. This is due to insufficient symlink protection.
node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic is insufficient when extracting tar files that contain both a directory and a symlink with the same name as the directory. This order of operations results in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped.
However, this is also where node-tar checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it is possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location.
Remediation
Upgrade tar to version 3.2.3, 4.4.15, 5.0.7, 6.1.2 or higher.
References
high severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Overwrite. This is due to insufficient absolute path sanitization.
node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservePaths flag is not set to true. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example, the path /home/user/.bashrc would turn into home/user/.bashrc.
This logic is insufficient when file paths contain repeated path roots such as ////home/user/.bashrc. node-tar only strips a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. ///home/user/.bashrc) still resolves to an absolute path.
Remediation
Upgrade tar to version 3.2.2, 4.4.14, 5.0.6, 6.1.1 or higher.
References
high severity
- Vulnerable module: ajv
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › har-validator@4.2.1 › ajv@4.11.8
Overview
ajv is an Another JSON Schema Validator
Affected versions of this package are vulnerable to Prototype Pollution. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade ajv to version 6.12.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Insecure Defaults. Insufficient policy enforcement in the File System API of chromium allows a remote attacker to bypass filesystem restrictions via a crafted HTML page.
Remediation
Upgrade electron to version 10.4.1, 11.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Write in the Compositing process. An attacker can potentially perform a sandbox escape by exploiting specific UI gestures. This is only exploitable if the attacker has already compromised the GPU process.
Remediation
Upgrade electron to version 27.3.11, 28.3.1, 29.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the WebGPU process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 26.6.5, 27.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the ANGLE component. An attacker can potentially exploit heap corruption by convincing a user to visit a crafted HTML page.
Remediation
Upgrade electron to version 26.6.5, 27.2.2 or higher.
References
high severity
- Vulnerable module: js-yaml
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › js-yaml@3.7.0
Overview
js-yaml is a human-friendly data serialization language.
Affected versions of this package are vulnerable to Arbitrary Code Execution. When an object with an executable toString() property used as a map key, it will execute that function. This happens only for load(), which should not be used with untrusted data anyway. safeLoad() is not affected because it can't parse functions.
Remediation
Upgrade js-yaml to version 3.13.1 or higher.
References
high severity
- Vulnerable module: ip
- Introduced through: ip@1.1.9
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › ip@1.1.9
Overview
ip is a Node library.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the ip.isPublic() and ip.isPrivate() functions. An attacker can interact with internal network resources by supplying specially crafted IP address such as octal localhost format ("017700000001") that is incorrectly identified as public.
Note:
This issue exists because of an incomplete fix for CVE-2024-29415.
PoC
Test octal localhost bypass:
node -e "const ip=require('ip'); console.log('017700000001 bypass:', ip.isPublic('017700000001'));" - returns true
Remediation
There is no fixed version for ip.
References
high severity
- Vulnerable module: ip
- Introduced through: ip@1.1.9
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › ip@1.1.9
Overview
ip is a Node library.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the ip.isPublic() and ip.isPrivate() functions. An attacker can interact with internal network resources by supplying specially crafted IP address such as null route ("0") that is being incorrectly identified as public.
Note: This issue exists because of an incomplete fix for CVE-2024-29415.
Exploit is only possible if the application and operating system interpret connection attempts to 0 or 0.0.0.0 as connections to 127.0.0.1.
PoC
Test null route bypass:
node -e "const ip=require('ip'); console.log('0 bypass:', ip.isPublic('0'));" - returns true
Remediation
There is no fixed version for ip.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@7.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Privilege Escalation. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.
##Note:
Only apps using contextIsolation are affected.
Remediation
Upgrade electron to version 7.2.4, 8.2.4 or higher.
References
high severity
- Vulnerable module: bl
- Introduced through: unirest@0.5.1
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › bl@1.1.2
Overview
bl is a library that allows you to collect buffers and access with a standard readable buffer interface.
Affected versions of this package are vulnerable to Uninitialized Memory Exposure. If user input ends up in consume() argument and can become negative, BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.
PoC by chalker
const { BufferList } = require('bl')
const secret = require('crypto').randomBytes(256)
for (let i = 0; i < 1e6; i++) {
const clone = Buffer.from(secret)
const bl = new BufferList()
bl.append(Buffer.from('a'))
bl.consume(-1024)
const buf = bl.slice(1)
if (buf.indexOf(clone) !== -1) {
console.error(`Match (at ${i})`, buf)
}
}
Remediation
Upgrade bl to version 2.2.1, 3.0.1, 4.0.3, 1.2.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@36.3.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Function Call with Incorrectly Specified Arguments via an incorrect handle provided in unspecified circumstances in Mojo. An attacker can reflect a broker-initiated transport back to a broker, which ultimately allows for handle leaks if the reflected transport is later used to deserialize another transport containing handles.
Remediation
Upgrade electron to version 36.3.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@7.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Privilege Escalation. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.
##Note:
Only apps using both contextIsolation and contextBridge are affected.
Remediation
Upgrade electron to version 7.2.4, 8.2.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Privilege Escalation. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.
##Note:
Only apps using contextIsolation are affected.
Remediation
Upgrade electron to version 6.1.11, 7.2.4, 8.2.4 or higher.
References
high severity
- Vulnerable module: netmask
- Introduced through: netmask@1.0.6
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › netmask@1.0.6Remediation: Upgrade to netmask@2.0.1.
Overview
netmask is a library to parse IPv4 CIDR blocks.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF). It incorrectly evaluates individual IPv4 octets that contain octal strings as left-stripped integers, leading to an inordinate attack surface on hundreds of thousands of projects that rely on netmask to filter or evaluate IPv4 block ranges, both inbound and outbound.
For example, a remote unauthenticated attacker can request local resources using input data 0177.0.0.1 (127.0.0.1), which netmask evaluates as the public IP 177.0.0.1.
Contrastingly, a remote authenticated or unauthenticated attacker can input the data 0127.0.0.01 (87.0.0.1) as localhost, yet the input data is a public IP and can potentially cause local and remote file inclusion (LFI/RFI).
A remote authenticated or unauthenticated attacker can bypass packages that rely on netmask to filter IP address blocks to reach intranets, VPNs, containers, adjacent VPC instances, or LAN hosts, using input data such as 012.0.0.1 (10.0.0.1), which netmask evaluates as 12.0.0.1 (public).
NOTE: This vulnerability has also been identified as: CVE-2021-29418
Remediation
Upgrade netmask to version 2.0.1 or higher.
References
high severity
- Vulnerable module: netmask
- Introduced through: netmask@1.0.6
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › netmask@1.0.6Remediation: Upgrade to netmask@2.0.1.
Overview
netmask is a library to parse IPv4 CIDR blocks.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF). It incorrectly evaluates individual IPv4 octets that contain octal strings as left-stripped integers, leading to an inordinate attack surface on hundreds of thousands of projects that rely on netmask to filter or evaluate IPv4 block ranges, both inbound and outbound.
For example, a remote unauthenticated attacker can request local resources using input data 0177.0.0.1 (127.0.0.1), which netmask evaluates as the public IP 177.0.0.1.
Contrastingly, a remote authenticated or unauthenticated attacker can input the data 0127.0.0.01 (87.0.0.1) as localhost, yet the input data is a public IP and can potentially cause local and remote file inclusion (LFI/RFI).
A remote authenticated or unauthenticated attacker can bypass packages that rely on netmask to filter IP address blocks to reach intranets, VPNs, containers, adjacent VPC instances, or LAN hosts, using input data such as 012.0.0.1 (10.0.0.1), which netmask evaluates as 12.0.0.1 (public).
NOTE: This vulnerability has also been identified as: CVE-2021-28918
Remediation
Upgrade netmask to version 2.0.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@25.9.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation in the USB component.
Remediation
Upgrade electron to version 25.9.4, 26.5.0, 27.0.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@25.9.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Integer Overflow or Wraparound in the USB component.
Remediation
Upgrade electron to version 25.9.4, 26.5.0, 27.0.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to NULL Pointer Dereference in V8, due to an object lifecycle issue involving scope inheritance.
Remediation
Upgrade electron to version 27.3.8, 28.2.9, 29.1.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.0.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Animation component in Chromium.
Remediation
Upgrade electron to version 16.0.10, 17.1.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in V8, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 19.1.7, 20.3.7 or higher.
References
high severity
- Vulnerable module: async
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-ros@SnappyRobotics/snappy-ros › rosnodejs@2.2.0 › async@2.0.1
Overview
Affected versions of this package are vulnerable to Prototype Pollution via the mapValues() method, due to improper check in createObjectIterator function.
PoC
//when objects are parsed, all properties are created as own (the objects can come from outside sources (http requests/ file))
const hasOwn = JSON.parse('{"__proto__": {"isAdmin": true}}');
//does not have the property, because it's inside object's own "__proto__"
console.log(hasOwn.isAdmin);
async.mapValues(hasOwn, (val, key, cb) => cb(null, val), (error, result) => {
// after the method executes, hasOwn.__proto__ value (isAdmin: true) replaces the prototype of the newly created object, leading to potential exploits.
console.log(result.isAdmin);
});
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade async to version 2.6.4, 3.2.2 or higher.
References
high severity
- Vulnerable module: bcrypt
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3
Overview
bcrypt is an A library to help you hash passwords.
Affected versions of this package are vulnerable to Insecure Encryption. Data is truncated wrong when its length is greater than 255 bytes.
Remediation
Upgrade bcrypt to version 5.0.0 or higher.
References
high severity
- Vulnerable module: braces
- Introduced through: nodemon@1.19.4
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › braces@2.3.2Remediation: Upgrade to nodemon@2.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › braces@2.3.2
Overview
braces is a Bash-like brace expansion, implemented in JavaScript.
Affected versions of this package are vulnerable to Excessive Platform Resource Consumption within a Loop due improper limitation of the number of characters it can handle, through the parse function. An attacker can cause the application to allocate excessive memory and potentially crash by sending imbalanced braces as input.
PoC
const { braces } = require('micromatch');
console.log("Executing payloads...");
const maxRepeats = 10;
for (let repeats = 1; repeats <= maxRepeats; repeats += 1) {
const payload = '{'.repeat(repeats*90000);
console.log(`Testing with ${repeats} repeats...`);
const startTime = Date.now();
braces(payload);
const endTime = Date.now();
const executionTime = endTime - startTime;
console.log(`Regex executed in ${executionTime / 1000}s.\n`);
}
Remediation
Upgrade braces to version 3.0.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@17.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Denial of Service (DoS) in PDF in Google Chrome, a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade electron to version 17.4.11, 18.3.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.14.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to insufficient validation of untrusted input in V8.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade electron to version 18.3.14 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to type confusion in V8, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 19.1.7, 20.3.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Denial of Service (DoS) via an Out of bounds memory access in V8.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade electron to version 27.3.6, 28.2.7, 29.1.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@8.5.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Freetype.
Remediation
Upgrade electron to version 8.5.3, 9.3.3, 10.1.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow via V8.
Remediation
Upgrade electron to version 10.4.4, 11.4.4, 12.0.6 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read. An unknown vunerability exists in Chrome which affects electron.
Remediation
Upgrade electron to version 9.4.1, 10.3.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. FileChooserImpl can outlive ListenerProxy leading to a crash.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. Initialize() could potentially run twice in MojoVideoEncodeAcceleratorService.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
high severity
- Vulnerable module: engine.io
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › engine.io@3.5.0
Overview
engine.io is a realtime engine behind Socket.IO. It provides the foundation of a bidirectional connection between client and server
Affected versions of this package are vulnerable to Denial of Service (DoS) via a POST request to the long polling transport.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade engine.io to version 3.6.0 or higher.
References
high severity
- Vulnerable module: engine.io
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › engine.io@3.5.0
Overview
engine.io is a realtime engine behind Socket.IO. It provides the foundation of a bidirectional connection between client and server
Affected versions of this package are vulnerable to Denial of Service (DoS). A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade engine.io to version 3.6.1, 6.2.1 or higher.
References
high severity
- Vulnerable module: fresh
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › fresh@0.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › send@0.14.1 › fresh@0.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2 › send@0.14.2 › fresh@0.3.0
Overview
fresh is HTTP response freshness testing.
Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. A Regular Expression (/ *, */) was used for parsing HTTP headers and take about 2 seconds matching time for 50k characters.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade fresh to version 0.5.2 or higher.
References
high severity
- Vulnerable module: i18next
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › i18next@1.10.6
Overview
i18next is an internationalization framework for browser or any other javascript environment (eg. node.js).
Affected versions of this package are vulnerable to Prototype Pollution via getLastOfPath() in i18next.js.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade i18next to version 19.8.5 or higher.
References
high severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Prototype Pollution through the zipObjectDeep function due to improper user input sanitization in the baseZipObject function.
PoC
lodash.zipobjectdeep:
const zipObjectDeep = require("lodash.zipobjectdeep");
let emptyObject = {};
console.log(`[+] Before prototype pollution : ${emptyObject.polluted}`);
//[+] Before prototype pollution : undefined
zipObjectDeep(["constructor.prototype.polluted"], [true]);
//we inject our malicious attributes in the vulnerable function
console.log(`[+] After prototype pollution : ${emptyObject.polluted}`);
//[+] After prototype pollution : true
lodash:
const test = require("lodash");
let emptyObject = {};
console.log(`[+] Before prototype pollution : ${emptyObject.polluted}`);
//[+] Before prototype pollution : undefined
test.zipObjectDeep(["constructor.prototype.polluted"], [true]);
//we inject our malicious attributes in the vulnerable function
console.log(`[+] After prototype pollution : ${emptyObject.polluted}`);
//[+] After prototype pollution : true
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade lodash to version 4.17.17 or higher.
References
high severity
- Vulnerable module: mailparser
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › mailparser@0.6.2
Overview
mailparser is an email parser.
Affected versions of this package are vulnerable to Denial of Service (DoS).
Overview
mailparser is an email parser.
Affected versions of this package are vulnerable to Denial of Service (DoS) attacks via a crafted email containing a few million multiparts.
MIME (Multipurpose Internet Mail Extentions) is an internet standard that extends the format of email to support: Non-ACSII character sets, non-text attachments, and more.
Most Node.js MIME decoders do not validate the number of multiparts they are willing to decode, allowing an attacker to send a crafted email containing a few million multiparts, which will then block the Node.js event loop for tens of seconds, explode RAM usage, and cause an out of memory crash.
Disclosure Timeline
- April 23rd, 2018 - Initial private disclosure to package owner
- April 24th, 2018 - Initial response from package owner
- June 25th, 2018 - Public disclosure
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade mailparser to version 2.3.0 or higher.
References
high severity
- Vulnerable module: moment
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-ros@SnappyRobotics/snappy-ros › rosnodejs@2.2.0 › moment@2.12.0
Overview
moment is a lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates.
Affected versions of this package are vulnerable to Directory Traversal when a user provides a locale string which is directly used to switch moment locale.
Details
A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.
Directory Traversal vulnerabilities can be generally divided into two types:
- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.
st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa
Note %2e is the URL encoded version of . (dot).
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
Zip-Slip.
One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:
2018-04-15 22:04:29 ..... 19 19 good.txt
2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
Remediation
Upgrade moment to version 2.29.2 or higher.
References
high severity
- Vulnerable module: nth-check
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › cheerio@0.22.0 › css-select@1.2.0 › nth-check@1.0.2
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) when parsing crafted invalid CSS nth-checks, due to the sub-pattern \s*(?:([+-]?)\s*(\d+))? in RE_NTH_ELEMENT with quantified overlapping adjacency.
PoC
var nthCheck = require("nth-check")
for(var i = 1; i <= 50000; i++) {
var time = Date.now();
var attack_str = '2n' + ' '.repeat(i*10000)+"!";
try {
nthCheck.parse(attack_str)
}
catch(err) {
var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
}
}
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade nth-check to version 2.0.1 or higher.
References
high severity
- Vulnerable module: parsejson
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › parsejson@0.0.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › parsejson@0.0.3
Overview
parsejson is a method that parses a JSON string and returns a JSON object.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. An attacker may pass a specially crafted JSON data, causing the server to hang.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
There is no fixed version for parsejson.
References
high severity
- Vulnerable module: qs
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › body-parser@1.15.2 › qs@6.2.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › qs@6.2.0
Overview
qs is a querystring parser that supports nesting and arrays, with a depth limit.
Affected versions of this package are vulnerable to Prototype Override Protection Bypass. By default qs protects against attacks that attempt to overwrite an object's existing prototype properties, such as toString(), hasOwnProperty(),etc.
From qs documentation:
By default parameters that would overwrite properties on the object prototype are ignored, if you wish to keep the data from those fields either use plainObjects as mentioned above, or set allowPrototypes to true which will allow user input to overwrite those properties. WARNING It is generally a bad idea to enable this option as it can cause problems when attempting to use the properties that have been overwritten. Always be careful with this option.
Overwriting these properties can impact application logic, potentially allowing attackers to work around security controls, modify data, make the application unstable and more.
In versions of the package affected by this vulnerability, it is possible to circumvent this protection and overwrite prototype properties and functions by prefixing the name of the parameter with [ or ]. e.g. qs.parse("]=toString") will return {toString = true}, as a result, calling toString() on the object will throw an exception.
Example:
qs.parse('toString=foo', { allowPrototypes: false })
// {}
qs.parse("]=toString", { allowPrototypes: false })
// {toString = true} <== prototype overwritten
For more information, you can check out our blog.
Disclosure Timeline
- February 13th, 2017 - Reported the issue to package owner.
- February 13th, 2017 - Issue acknowledged by package owner.
- February 16th, 2017 - Partial fix released in versions
6.0.3,6.1.1,6.2.2,6.3.1. - March 6th, 2017 - Final fix released in versions
6.4.0,6.3.2,6.2.3,6.1.2and6.0.4
Remediation
Upgrade qs to version 6.0.4, 6.1.2, 6.2.3, 6.3.2 or higher.
References
high severity
- Vulnerable module: qs
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › body-parser@1.15.2 › qs@6.2.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › qs@6.2.0
Overview
qs is a querystring parser that supports nesting and arrays, with a depth limit.
Affected versions of this package are vulnerable to Prototype Poisoning which allows attackers to cause a Node process to hang, processing an Array object whose prototype has been replaced by one with an excessive length value.
Note: In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade qs to version 6.2.4, 6.3.3, 6.4.1, 6.5.3, 6.6.1, 6.7.3, 6.8.3, 6.9.7, 6.10.3 or higher.
References
high severity
- Vulnerable module: semver
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › semver@5.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › imap@0.8.19 › utf7@1.0.2 › semver@5.3.0
Overview
semver is a semantic version parser used by npm.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.
PoC
const semver = require('semver')
const lengths_2 = [2000, 4000, 8000, 16000, 32000, 64000, 128000]
console.log("n[+] Valid range - Test payloads")
for (let i = 0; i =1.2.3' + ' '.repeat(lengths_2[i]) + '<1.3.0';
const start = Date.now()
semver.validRange(value)
// semver.minVersion(value)
// semver.maxSatisfying(["1.2.3"], value)
// semver.minSatisfying(["1.2.3"], value)
// new semver.Range(value, {})
const end = Date.now();
console.log('length=%d, time=%d ms', value.length, end - start);
}
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade semver to version 5.7.2, 6.3.1, 7.5.2 or higher.
References
high severity
- Vulnerable module: socket.io-parser
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1
Overview
socket.io-parser is a socket.io protocol parser
Affected versions of this package are vulnerable to Denial of Service (DoS) via a large packet because a concatenation approach is used.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade socket.io-parser to version 3.3.2, 3.4.1 or higher.
References
high severity
- Vulnerable module: unset-value
- Introduced through: nodemon@1.19.4
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
Overview
Affected versions of this package are vulnerable to Prototype Pollution via the unset function in index.js, because it allows access to object prototype properties.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade unset-value to version 2.0.1 or higher.
References
high severity
- Vulnerable module: ws
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › engine.io@3.5.0 › ws@7.4.6
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of this package are vulnerable to Denial of Service (DoS) when the number of received headers exceed the server.maxHeadersCount or request.maxHeadersCount threshold.
Workaround
This issue can be mitigating by following these steps:
Reduce the maximum allowed length of the request headers using the
--max-http-header-size=sizeand/or themaxHeaderSizeoptions so that no more headers than theserver.maxHeadersCountlimit can be sent.Set
server.maxHeadersCountto 0 so that no limit is applied.
PoC
const http = require('http');
const WebSocket = require('ws');
const server = http.createServer();
const wss = new WebSocket.Server({ server });
server.listen(function () {
const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
const headers = {};
let count = 0;
for (let i = 0; i < chars.length; i++) {
if (count === 2000) break;
for (let j = 0; j < chars.length; j++) {
const key = chars[i] + chars[j];
headers[key] = 'x';
if (++count === 2000) break;
}
}
headers.Connection = 'Upgrade';
headers.Upgrade = 'websocket';
headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
headers['Sec-WebSocket-Version'] = '13';
const request = http.request({
headers: headers,
host: '127.0.0.1',
port: server.address().port
});
request.end();
});
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade ws to version 5.2.4, 6.2.3, 7.5.10, 8.17.1 or higher.
References
high severity
- Vulnerable module: ws
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › ws@1.1.1
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of this package are vulnerable to Denial of Service (DoS)
attacks. A specially crafted value of the Sec-WebSocket-Extensions header that used Object.prototype property names as extension or parameter names could be used to make a ws server crash.
PoC:
const WebSocket = require('ws');
const net = require('net');
const wss = new WebSocket.Server({ port: 3000 }, function () {
const payload = 'constructor'; // or ',;constructor'
const request = [
'GET / HTTP/1.1',
'Connection: Upgrade',
'Sec-WebSocket-Key: test',
'Sec-WebSocket-Version: 8',
`Sec-WebSocket-Extensions: ${payload}`,
'Upgrade: websocket',
'\r\n'
].join('\r\n');
const socket = net.connect(3000, function () {
socket.resume();
socket.write(request);
});
});
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade ws to version 1.1.5, 3.3.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read via the IPC in chromium.
Remediation
Upgrade electron to version 11.4.4, 10.4.4 or higher.
References
high severity
- Vulnerable module: hawk
- Introduced through: serialport@4.0.7, unirest@0.5.1 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3
Overview
hawk is a library for the HTTP Hawk Authentication Scheme.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in header parsing where each added character in the attacker's input increases the computation time exponentially.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade hawk to version 9.0.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@5.0.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Arbitrary Code Execution due to Node being enabled in a webview because the default values of nodeIntegration and webviewTag were set to true when they where undefined by a user. The fix allows users to prevent Node and webview being enabled, when undefined, by setting the default values of nodeIntegration and webviewTag to false.
Remediation
Upgrade electron to version 5.0.0-beta.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Buffer Overflow in ANGLE.
Remediation
Upgrade electron to version 13.5.0, 12.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Reader Mode.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in History.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Media Feeds.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.5.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow via the Blink module in Chromium.
Remediation
Upgrade electron to version 14.2.0, 13.5.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.2.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in WebGPU.
Remediation
Upgrade electron to version 16.2.5, 17.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in V8 Internationalization.
Remediation
Upgrade electron to version 15.5.6, 16.2.7, 17.4.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Crashpad in Google Chrome on Android, which allows a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Remediation
Upgrade electron to version 19.1.7, 20.3.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@20.3.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Network Service via a crafted HTML page and specific interactions.
Remediation
Upgrade electron to version 20.3.10, 21.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@21.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Metrics by allowing a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 21.4.4, 22.3.5 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@22.3.25.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in vp8 encoding in libvpx.
Remediation
Upgrade electron to version 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the WebRTC framework, used to provide Real-Time Communications (RTC) capabilities via JavaScript APIs.
Remediation
Upgrade electron to version 26.6.3, 27.2.0, 28.1.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the ANGLE process. An attacker can perform an out of bounds memory read via a crafted HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the Dawn process. An attacker can perform an out of bounds memory write by exploiting a crafted HTML page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Check or Handling of Exceptional Conditions which returns an invalid handle after ReportBadMessage
Remediation
Upgrade electron to version 14.2.7, 15.4.0, 16.0.10 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation in Blink Editing.
Remediation
Upgrade electron to version 15.5.4, 16.2.6, 17.4.3, 18.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Validation. The value of a node was accessed without prior HasValue check. With WebAssembly this node is not guaranteed to be a value.
Remediation
Upgrade electron to version 10.1.6, 9.4.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Inappropriate implementation in Input.
Remediation
Upgrade electron to version 15.5.5, 16.2.6, 17.4.4, 18.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Insufficient Validation in V8.
Remediation
Upgrade electron to version 9.4.0, 10.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Insufficient Validation via an unknown issue in chromium.
Remediation
Upgrade electron to version 9.4.2, 10.3.1, 11.2.2 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds in ANGLE.
Remediation
Upgrade electron to version 13.5.0, 12.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read. The input to sctp_load_addresses_from_init is verified by calling sctp_arethere_unrecognized_parameters, however there is a difference in how these functions handle parameter bounds. The function sctp_arethere_unrecognized_parameters does not process a parameter that is partially outside of the limit of the chunk, meanwhile, sctp_load_addresses_from_init will continue processing until a parameter that is entirely outside of the chunk occurs.
This means that the last parameter of a chunk is not always verified, which can lead to parameters with very short plen values being processed by sctp_load_addresses_from_init. This can lead to out-of-bounds reads whenever the plen is subtracted from the header len.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Race Condition in Aura.
Remediation
Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion due to mishandling of interceptors which can lead to out-of-bounds memory access.
Remediation
Upgrade electron to version 15.5.0, 16.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8.
Remediation
Upgrade electron to version 15.5.3, 16.2.3, 17.4.1 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion due to a type confusion in V8. A remote attacker could exploit heap corruption via a crafted HTML page.
Note: The Stable channel has been updated to 120.0.6099.234 for Mac devices.
Remediation
Upgrade electron to version 26.6.6, 27.2.3, 28.1.4 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in V8.
Remediation
Upgrade electron to version 13.6.6, 14.2.4 or higher.
References
high severity
- Vulnerable module: follow-redirects
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › follow-redirects@1.2.1
Overview
Affected versions of this package are vulnerable to Improper Handling of Extra Parameters due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.
PoC
# Case 1 : Bypassing localhost restriction
let url = 'http://[localhost]/admin';
try{
new URL(url); // ERROR : Invalid URL
}catch{
url.parse(url); // -> http://localhost/admin
}
# Case 2 : Bypassing domain restriction
let url = 'http://attacker.domain*.allowed.domain:a';
try{
new URL(url); // ERROR : Invalid URL
}catch{
url.parse(url); // -> http://attacker.domain/*.allowed.domain:a
}
Remediation
Upgrade follow-redirects to version 1.15.4 or higher.
References
high severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
PoC by Snyk
const mergeFn = require('lodash').defaultsDeep;
const payload = '{"constructor": {"prototype": {"a0": true}}}'
function check() {
mergeFn({}, JSON.parse(payload));
if (({})[`a0`] === true) {
console.log(`Vulnerable to Prototype Pollution via ${payload}`);
}
}
check();
For more information, check out our blog post
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade lodash to version 4.17.12 or higher.
References
high severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Prototype Pollution via the set and setwith functions due to improper user input sanitization.
PoC
lod = require('lodash')
lod.set({}, "__proto__[test2]", "456")
console.log(Object.prototype)
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade lodash to version 4.17.17 or higher.
References
high severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Prototype Pollution. The functions merge, mergeWith, and defaultsDeep could be tricked into adding or modifying properties of Object.prototype. This is due to an incomplete fix to CVE-2018-3721.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade lodash to version 4.17.11 or higher.
References
high severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Code Injection via template.
PoC
var _ = require('lodash');
_.template('', { variable: '){console.log(process.env)}; with(obj' })()
Remediation
Upgrade lodash to version 4.17.21 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@22.3.16.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read in WebRTC, exploitable via a crafted HTML page.
Remediation
Upgrade electron to version 22.3.16 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@26.6.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Media Stream process. An attacker can potentially exploit heap corruption by crafting a malicious HTML page.
Remediation
Upgrade electron to version 26.6.3, 27.2.0 or higher.
References
high severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-bounds Read in Skia.
Remediation
Upgrade electron to version 31.7.2, 32.2.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') via a crafted HTML page. An attacker can potentially exploit heap corruption.
Remediation
Upgrade electron to version 31.7.4, 32.2.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.2.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') via a crafted HTML page. An attacker can potentially exploit heap corruption.
Remediation
Upgrade electron to version 32.2.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access Restriction Bypass due to an inappropriate implementation in the Extensions feature. An attacker can bypass site isolation.
Remediation
Upgrade electron to version 31.7.5, 32.2.5, 33.2.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Fonts.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow through the V8 engine.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@32.3.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in v8, when processing a very large number of parameters.
Remediation
Upgrade electron to version 32.3.2, 33.4.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@33.4.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Isolation or Compartmentalization that allows an attacker who can convince a user to follow a malicious link to escape sandbox protections, due to a logic error in the Mojo component. This vulnerability does not enable code execution on its own, but is presumed chainable with another vulnerability to achieve code execution and has been observed in the wild.
Note: This vulnerability is only exploitable on Windows.
Remediation
Upgrade electron to version 33.4.8, 34.4.1, 35.1.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@37.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Integer Overflow or Wraparound via an incorrect count being passed to InstructionAccurateScope in the V8 engine. An attacker can cause heap corruption by enticing a user to visit a specially crafted HTML page.
Remediation
Upgrade electron to version 37.2.4 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@31.7.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion. An attacker can access memory locations outside of the intended bounds by crafting a malicious HTML page that triggers type confusion in the V8 engine.
Remediation
Upgrade electron to version 31.7.2 or higher.
References
medium severity
- Vulnerable module: js-yaml
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › js-yaml@3.7.0
Overview
js-yaml is a human-friendly data serialization language.
Affected versions of this package are vulnerable to Prototype Pollution via the merge function. An attacker can alter object prototypes by supplying specially crafted YAML documents containing __proto__ properties. This can lead to unexpected behavior or security issues in applications that process untrusted YAML input.
Workaround
This vulnerability can be mitigated by running the server with node --disable-proto=delete or by using Deno, which has pollution protection enabled by default.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade js-yaml to version 3.14.2, 4.1.1 or higher.
References
medium severity
- Vulnerable module: nodemailer
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › nodemailer@1.11.0
Overview
nodemailer is an Easy as cake e-mail sending from your Node.js applications
Affected versions of this package are vulnerable to Interpretation Conflict due to improper handling of quoted local-parts containing @. An attacker can cause emails to be sent to unintended external recipients or bypass domain-based access controls by crafting specially formatted email addresses with quoted local-parts containing the @ character.
Remediation
Upgrade nodemailer to version 7.0.7 or higher.
References
medium severity
- Vulnerable module: path-to-regexp
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › path-to-regexp@0.1.7
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) when including multiple regular expression parameters in a single segment, which will produce the regular expression /^\/([^\/]+?)-([^\/]+?)\/?$/, if two parameters within a single segment are separated by a character other than a / or .. Poor performance will block the event loop and can lead to a DoS.
Note:
While the 8.0.0 release has completely eliminated the vulnerable functionality, prior versions that have received the patch to mitigate backtracking may still be vulnerable if custom regular expressions are used. So it is strongly recommended for regular expression input to be controlled to avoid malicious performance degradation in those versions. This behavior is enforced as of version 7.1.0 via the strict option, which returns an error if a dangerous regular expression is detected.
Workaround
This vulnerability can be avoided by using a custom regular expression for parameters after the first in a segment, which excludes - and /.
PoC
/a${'-a'.repeat(8_000)}/a
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade path-to-regexp to version 0.1.10, 1.9.0, 3.3.0, 6.3.0, 8.0.0 or higher.
References
medium severity
- Vulnerable module: path-to-regexp
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › path-to-regexp@0.1.7
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) when including multiple regular expression parameters in a single segment, when the separator is not . (e.g. no /:a-:b). Poor performance will block the event loop and can lead to a DoS.
Note:
This issue is caused due to an incomplete fix for CVE-2024-45296.
Workarounds
This can be mitigated by avoiding using two parameters within a single path segment, when the separator is not . (e.g. no /:a-:b). Alternatively, the regex used for both parameters can be defined to ensure they do not overlap to allow backtracking.
PoC
/a${'-a'.repeat(8_000)}/a
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade path-to-regexp to version 0.1.12 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@7.2.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Arbitrary File Read. It allows arbitrary local file read by defining unsafe window options on a child window opened via window.open.
Remediation
Upgrade electron to version 7.2.4, 8.2.4 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Integer Overflow or Wraparound when decoding videos with a large frame size. An attacker can cause memory corruption within the AV1 decoder by providing a specially crafted video file.
Remediation
Upgrade electron to version 27.3.11, 28.3.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.2.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via Angle, where base level changes may not update FBO completeness check.
Remediation
Upgrade electron to version 16.2.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free. The rendering_orphan_handlers_ and deletable_orphan_handlers_ handlers can hold references to the context after BaseAudioContext is destroyed.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.
References
medium severity
- Vulnerable module: jsonwebtoken
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › jsonwebtoken@7.4.3
Overview
jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm such that the library can be misconfigured to use legacy, insecure key types for signature verification. For example, DSA keys could be used with the RS256 algorithm.
Exploitability
Users are affected when using an algorithm and a key type other than the combinations mentioned below:
EC: ES256, ES384, ES512
RSA: RS256, RS384, RS512, PS256, PS384, PS512
RSA-PSS: PS256, PS384, PS512
And for Elliptic Curve algorithms:
ES256: prime256v1
ES384: secp384r1
ES512: secp521r1
Workaround
Users who are unable to upgrade to the fixed version can use the allowInvalidAsymmetricKeyTypes option to true in the sign() and verify() functions to continue usage of invalid key type/algorithm combination in 9.0.0 for legacy compatibility.
Remediation
Upgrade jsonwebtoken to version 9.0.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation which allows attackers who have control over a given app's update server or update storage to serve maliciously crafted update packages that pass the code signing validation check but contain malicious code in some components.
Remediation
Upgrade electron to version 15.5.0, 16.2.0, 17.2.0, 18.0.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access Restriction Bypass. Inappropriate implementation in Referrer in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. This vulnerability relates to an electron component.
Remediation
Upgrade electron to version 10.4.3, 11.4.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.0.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Domain Spoofing via a crafted HTML page as a result of inappropriate implementation in navigation in Google Chrome.
Remediation
Upgrade electron to version 16.0.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in WebGL via Chrome. This allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 13.1.8, 12.0.16, 11.4.11 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation via the File System API.
Remediation
Upgrade electron to version 11.2.1, 9.4.4 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@17.4.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation in Data Transfer, because the sanitization code only does one round of parsing and serializing.
Remediation
Upgrade electron to version 17.4.8, 18.3.5 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Inappropriate Implementation via cache in Google Chrome. This allows a remote attacker to leak cross-origin data via a crafted HTML page.
Remediation
Upgrade electron to version 13.6.6, 14.2.2, 15.3.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure. When a BigInt is right-shifted the backing store is not properly cleared, allowing uninitialized memory to be read.
Remediation
Upgrade electron to version 9.4.1, 10.3.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure via the core module in Chromium.
Remediation
Upgrade electron to version 14.2.0, 13.5.2, 12.2.2 or higher.
References
medium severity
- Vulnerable module: follow-redirects
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › follow-redirects@1.2.1
Overview
Affected versions of this package are vulnerable to Information Exposure due to the handling of the Proxy-Authorization header across hosts. When using a dependent library, it only clears the authorization header during cross-domain redirects but allows the proxy-authentication header, which contains credentials, to persist. This behavior may lead to the unintended leakage of credentials if an attacker can trigger a cross-domain redirect and capture the persistent proxy-authentication header.
PoC
const axios = require('axios');
axios.get('http://127.0.0.1:10081/',{
headers: {
'AuThorization': 'Rear Test',
'ProXy-AuthoriZation': 'Rear Test',
'coOkie': 't=1'
}
}).then(function (response) {
console.log(response);
})
Remediation
Upgrade follow-redirects to version 1.15.6 or higher.
References
medium severity
- Vulnerable module: ip
- Introduced through: ip@1.1.9
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › ip@1.1.9
Overview
ip is a Node library.
Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) via the isPublic function, which identifies some private IP addresses as public addresses due to improper parsing of the input.
An attacker can manipulate a system that uses isLoopback(), isPrivate() and isPublic functions to guard outgoing network requests to treat certain IP addresses as globally routable by supplying specially crafted IP addresses.
Note
This vulnerability derived from an incomplete fix for CVE-2023-42282
Remediation
There is no fixed version for ip.
References
medium severity
- Vulnerable module: jsonwebtoken
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › jsonwebtoken@7.4.3
Overview
jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)
Affected versions of this package are vulnerable to Improper Restriction of Security Token Assignment via the secretOrPublicKey argument due to misconfigurations of the key retrieval function jwt.verify(). Exploiting this vulnerability might result in incorrect verification of forged tokens when tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm.
Note:
This vulnerability affects your application if it supports the usage of both symmetric and asymmetric keys in jwt.verify() implementation with the same key retrieval function.
Remediation
Upgrade jsonwebtoken to version 9.0.0 or higher.
References
medium severity
- Vulnerable module: request
- Introduced through: snappy-core@github:snappyrobotics/snappy-core, electron@1.8.8 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › ascii-art@1.5.1 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8 › electron-download@3.3.0 › nugget@2.2.0 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-feedparser@0.1.16 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-twitter@0.1.15 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › request@2.88.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › picture-tube@1.0.0 › request@2.9.203
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0
Overview
request is a simplified http request client.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to insufficient checks in the lib/redirect.js file by allowing insecure redirects in the default configuration, via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP).
NOTE: request package has been deprecated, so a fix is not expected. See https://github.com/request/request/issues/3142.
Remediation
A fix was pushed into the master branch but not yet published.
References
medium severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to the lack of folders count validation during the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running the software and even crash the client within few seconds of running it using a path with too many sub-folders inside.
Remediation
Upgrade tar to version 6.2.1 or higher.
References
medium severity
- Vulnerable module: tough-cookie
- Introduced through: snappy-core@github:snappyrobotics/snappy-core, electron@1.8.8 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › ascii-art@1.5.1 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8 › electron-download@3.3.0 › nugget@2.2.0 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-feedparser@0.1.16 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-twitter@0.1.15 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › request@2.88.2 › tough-cookie@2.5.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › tough-cookie@2.3.4
Overview
tough-cookie is a RFC6265 Cookies and CookieJar module for Node.js.
Affected versions of this package are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. Due to an issue with the manner in which the objects are initialized, an attacker can expose or modify a limited amount of property information on those objects. There is no impact to availability.
PoC
// PoC.js
async function main(){
var tough = require("tough-cookie");
var cookiejar = new tough.CookieJar(undefined,{rejectPublicSuffixes:false});
// Exploit cookie
await cookiejar.setCookie(
"Slonser=polluted; Domain=__proto__; Path=/notauth",
"https://__proto__/admin"
);
// normal cookie
var cookie = await cookiejar.setCookie(
"Auth=Lol; Domain=google.com; Path=/notauth",
"https://google.com/"
);
//Exploit cookie
var a = {};
console.log(a["/notauth"]["Slonser"])
}
main();
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade tough-cookie to version 4.1.3 or higher.
References
medium severity
- Vulnerable module: json5
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › i18next@1.10.6 › json5@0.2.0
Overview
Affected versions of this package are vulnerable to Prototype Pollution via the parse method , which does not restrict parsing of keys named __proto__, allowing specially crafted strings to pollute the prototype of the resulting object. This pollutes the prototype of the object returned by JSON5.parse and not the global Object prototype (which is the commonly understood definition of Prototype Pollution). Therefore, the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade json5 to version 1.0.2, 2.2.2 or higher.
References
medium severity
- Vulnerable module: jsonwebtoken
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › jsonwebtoken@7.4.3
Overview
jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)
Affected versions of this package are vulnerable to Improper Authentication such that the lack of algorithm definition in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification.
Exploitability
Users are affected only if all of the following conditions are true for the jwt.verify() function:
A token with no signature is received.
No algorithms are specified.
A falsy (e.g.,
null,false,undefined) secret or key is passed.
Remediation
Upgrade jsonwebtoken to version 9.0.0 or higher.
References
medium severity
- Vulnerable module: cookie
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › cookie-parser@1.4.3 › cookie@0.3.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › cookie@0.3.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › engine.io@3.5.0 › cookie@0.4.2
Overview
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the cookie name, path, or domain, which can be used to set unexpected values to other cookie fields.
Workaround
Users who are not able to upgrade to the fixed version should avoid passing untrusted or arbitrary values for the cookie fields and ensure they are set by the application instead of user input.
Details
Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
Types of attacks
There are a few methods by which XSS can be manipulated:
| Type | Origin | Description |
|---|---|---|
| Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
| Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
| DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
| Mutated | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
Affected environments
The following environments are susceptible to an XSS attack:
- Web servers
- Application servers
- Web application environments
How to prevent
This section describes the top best practices designed to specifically protect your code:
- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as
?,&,/,<,>and spaces to their respective HTML or URL encoded equivalents. - Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
Remediation
Upgrade cookie to version 0.7.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@19.1.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation in file system.
Remediation
Upgrade electron to version 19.1.5, 21.2.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion in V8.
Remediation
Upgrade electron to version 15.5.3, 16.2.4, 17.4.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free in Network service.
Remediation
Upgrade electron to version 12.0.13, 11.4.10 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@11.4.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via sqlite. This can allow a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Remediation
Upgrade electron to version 13.1.8, 12.0.16, 11.4.11 or higher.
References
medium severity
- Vulnerable module: hoek
- Introduced through: serialport@4.0.7, unirest@0.5.1 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › jsonwebtoken@7.4.3 › joi@6.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › jsonwebtoken@7.4.3 › joi@6.10.1 › topo@1.1.0 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › sntp@1.0.9 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › request@2.81.0 › hawk@3.1.3 › cryptiles@2.0.5 › boom@2.10.1 › hoek@2.16.3Remediation: Open PR to patch hoek@2.16.3.
Overview
hoek is an Utility methods for the hapi ecosystem.
Affected versions of this package are vulnerable to Prototype Pollution. The utilities function allow modification of the Object prototype. If an attacker can control part of the structure passed to this function, they could add or modify an existing property.
PoC by Olivier Arteau (HoLyVieR)
var Hoek = require('hoek');
var malicious_payload = '{"__proto__":{"oops":"It works !"}}';
var a = {};
console.log("Before : " + a.oops);
Hoek.merge({}, JSON.parse(malicious_payload));
console.log("After : " + a.oops);
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade hoek to version 4.2.1, 5.0.3 or higher.
References
medium severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Prototype Pollution. The utilities function allow modification of the Object prototype. If an attacker can control part of the structure passed to this function, they could add or modify an existing property.
PoC by Olivier Arteau (HoLyVieR)
var _= require('lodash');
var malicious_payload = '{"__proto__":{"oops":"It works !"}}';
var a = {};
console.log("Before : " + a.oops);
_.merge({}, JSON.parse(malicious_payload));
console.log("After : " + a.oops);
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade lodash to version 4.17.5 or higher.
References
medium severity
- Vulnerable module: nodemailer
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › nodemailer@1.11.0
Overview
nodemailer is an Easy as cake e-mail sending from your Node.js applications
Affected versions of this package are vulnerable to HTTP Header Injection if unsanitized user input that may contain newlines and carriage returns is passed into an address object.
PoC:
const userEmail = 'foo@bar.comrnSubject: foobar'; // imagine this comes from e.g. HTTP request params or is otherwise user-controllable
await transporter.sendMail({
from: '...',
to: '...',
replyTo: {
name: 'Customer',
address: userEmail,
},
subject: 'My Subject',
text: message,
});
Remediation
Upgrade nodemailer to version 6.6.1 or higher.
References
medium severity
- Vulnerable module: bunyan
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-ros@SnappyRobotics/snappy-ros › rosnodejs@2.2.0 › bunyan@1.8.1
Overview
bunyan is an a JSON logging library for node.js services
Affected versions of this package are vulnerable to Remote Code Execution (RCE) via insecure command formatting which allowed creating a "hacked" file in the current dir.
Remediation
Upgrade bunyan to version 1.8.13, 2.0.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Race Condition via a crafted Chrome Extension. An attacker who convinced a user to install a malicious extension can inject scripts or HTML into a privileged page.
Remediation
Upgrade electron to version 29.4.6, 30.4.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@27.3.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the xmlTextReader module. An attacker can cause denial of service by processing crafted XML documents with DTD validation and XInclude expansion enabled.
Remediation
Upgrade electron to version 27.3.5, 28.2.6 or higher.
References
medium severity
- Vulnerable module: inflight
- Introduced through: serialport@4.0.7, electron@1.8.8 and others
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8 › electron-download@3.3.0 › fs-extra@0.30.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › mqtt@2.2.1 › help-me@1.1.0 › glob-stream@6.1.0 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › mqtt@2.18.9 › help-me@1.1.0 › glob-stream@6.1.0 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › mqtt@2.18.9 › help-me@1.1.0 › glob-stream@6.1.0 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-ros@SnappyRobotics/snappy-ros › rosnodejs@2.2.0 › bunyan@1.8.1 › mv@2.1.1 › rimraf@2.4.5 › glob@6.0.4 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › fstream-ignore@1.0.5 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Overview
Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime via the makeres function due to improperly deleting keys from the reqs object after execution of callbacks. This behavior causes the keys to remain in the reqs object, which leads to resource exhaustion.
Exploiting this vulnerability results in crashing the node process or in the application crash.
Note: This library is not maintained, and currently, there is no fix for this issue. To overcome this vulnerability, several dependent packages have eliminated the use of this library.
To trigger the memory leak, an attacker would need to have the ability to execute or influence the asynchronous operations that use the inflight module within the application. This typically requires access to the internal workings of the server or application, which is not commonly exposed to remote users. Therefore, “Attack vector” is marked as “Local”.
PoC
const inflight = require('inflight');
function testInflight() {
let i = 0;
function scheduleNext() {
let key = `key-${i++}`;
const callback = () => {
};
for (let j = 0; j < 1000000; j++) {
inflight(key, callback);
}
setImmediate(scheduleNext);
}
if (i % 100 === 0) {
console.log(process.memoryUsage());
}
scheduleNext();
}
testInflight();
Remediation
There is no fixed version for inflight.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@22.3.24.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Insufficient Verification of Data Authenticity when the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses are enabled.
An attacker can edit files inside the .app bundle on macOS, which these fuses are supposed to protect against, by gaining write access to the filesystem from which the app is launched.
Note
This is only exploitable if your app is launched from a filesystem the attacker has write access to and is specific to macOS, as these fuses are only supported on macOS.
Remediation
Upgrade electron to version 22.3.24, 24.8.3, 25.8.1, 26.2.1 or higher.
References
medium severity
- Vulnerable module: express
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0
Overview
express is a minimalist web framework.
Affected versions of this package are vulnerable to Open Redirect due to the implementation of URL encoding using encodeurl before passing it to the location header. This can lead to unexpected evaluations of malformed URLs by common redirect allow list implementations in applications, allowing an attacker to bypass a properly implemented allow list and redirect users to malicious sites.
Remediation
Upgrade express to version 4.19.2, 5.0.0-beta.3 or higher.
References
medium severity
- Vulnerable module: bcrypt
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3
Overview
bcrypt is an A library to help you hash passwords.
Affected versions of this package are vulnerable to Cryptographic Issues. When hashing a password containing an ASCII NUL character, that character acts as the string terminator. Any following characters are ignored.
Remediation
Upgrade bcrypt to version 5.0.0 or higher.
References
medium severity
- Vulnerable module: canvas
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › ascii-art@1.5.1 › canvas@1.6.9
Overview
canvas is a Cairo-backed Canvas implementation for Node.js.
Affected versions of this package are vulnerable to Denial of Service (DoS). Processing malicious JPEGs or GIFs files could crash the node process.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade canvas to version 1.6.10 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Access Control Bypass due to insufficient policy enforcement in Cookies.
Remediation
Upgrade electron to version 18.3.9, 19.0.12 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@17.4.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Protection Mechanism Failure in File System API.
Remediation
Upgrade electron to version 17.4.9, 18.3.6, 19.0.7 or higher.
References
medium severity
- Vulnerable module: js-yaml
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › js-yaml@3.7.0
Overview
js-yaml is a human-friendly data serialization language.
Affected versions of this package are vulnerable to Denial of Service (DoS). The parsing of a specially crafted YAML file may exhaust the system resources.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade js-yaml to version 3.13.0 or higher.
References
medium severity
- Vulnerable module: moment
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-ros@SnappyRobotics/snappy-ros › rosnodejs@2.2.0 › moment@2.12.0Remediation: Open PR to patch moment@2.12.0.
Overview
moment is a lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates.
Affected versions of the package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks for any locale that has separate format and standalone options and format input can be controlled by the user.
An attacker can provide a specially crafted input to the format function, which nearly matches the pattern being matched. This will cause the regular expression matching to take a long time, all the while occupying the event loop and preventing it from processing other requests and making the server unavailable (a Denial of Service attack).
Disclosure Timeline
- October 19th, 2016 - Reported the issue to package owner.
- October 19th, 2016 - Issue acknowledged by package owner.
- October 24th, 2016 - Issue fixed and version
2.15.2released.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.7.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure in that it reveals hashed credentials when the target of a redirect is an SMB URL, such as one using the file:// scheme.
NOTE: This vulnerability is only exploitable on Windows.
Workaround
This vulnerability can be worked around by preventing redirects to file:// URLs in the WebContents.on('will-redirect') event.
Remediation
Upgrade electron to version 18.3.7, 19.0.11, 20.0.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@6.1.10.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Buffer Underflow. Since there may be multiple instance of DWriteFontProxyImpl instantiated for multiple RenderProcessHosts, and DWriteFontProxyImpl::GetUniqueNameLookupTable may access DWriteFontLookupTableBuilder::QueueShareMemoryRegionWhenReady from separate threads, there may be race conditions around the pending_callbacks_ member of DWriteFontLookupTableBuilder.
Remediation
Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Buffer Overflow when changing the PDF layout confuses AddFindResult() and causes it to fail a DCHECK()
Remediation
Upgrade electron to version 18.3.8, 19.0.13 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Control of a Resource Through its Lifetime in the FramebufferAttachment::mRenderToTextureSamples method in Angle. It was never updated if the renderbuffer storage was changed after attaching to framebuffer.
Remediation
Upgrade electron to version 13.6.8, 14.2.4, 15.3.6 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@16.2.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Inappropriate implementation in WebGL.
Remediation
Upgrade electron to version 16.2.5, 17.4.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Inappropriate implementation in Web Cursor.
Remediation
Upgrade electron to version 15.5.4, 16.2.3, 17.4.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Inappropriate Implementation via service workers in Google Chrome. This allows a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page.
Remediation
Upgrade electron to version 14.2.2, 15.3.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@8.5.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure. Electron before versions 11.0.0-beta.6, 10.1.2, 9.3.1 or 8.5.2 is vulnerable to a context isolation bypass. Apps using both contextIsolation and sandbox: true are affected. Apps using both contextIsolation and nodeIntegrationInSubFrames: true are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.
Remediation
Upgrade electron to version 8.5.2, 9.3.1, 10.1.2, 11.0.0-beta.6 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Sandbox Bypass via chromium, due to a child process's delayed integrity level not being set correctly.
Remediation
Upgrade electron to version 12.2.2, 13.5.2, 14.2.0 or higher.
References
medium severity
- Vulnerable module: minimist
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › poplib@0.1.7 › optimist@0.6.1 › minimist@0.0.10
Overview
minimist is a parse argument options module.
Affected versions of this package are vulnerable to Prototype Pollution. The library could be tricked into adding or modifying properties of Object.prototype using a constructor or __proto__ payload.
PoC by Snyk
require('minimist')('--__proto__.injected0 value0'.split(' '));
console.log(({}).injected0 === 'value0'); // true
require('minimist')('--constructor.prototype.injected1 value1'.split(' '));
console.log(({}).injected1 === 'value1'); // true
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade minimist to version 0.2.1, 1.2.3 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Exposure of Resource to Wrong Sphere which allows a renderer with JS execution to obtain access to a new renderer process even without nodeIntegrationInSubFrames being enabled, that allows effective access to ipcRenderer.
Remediation
Upgrade electron to version 15.5.6, 16.2.6, 17.2.0, 18.0.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@28.3.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Heap-based Buffer Overflow. The nativeImage.createFromPath or nativeImage.createFromBuffer APIs in Electron, which make use of Chromium's JPEGCodec::Decode, are vulnerable to a heap-based buffer overflow. An attacker can execute arbitrary code or cause a crash by supplying specially crafted image data.
Remediation
Upgrade electron to version 28.3.2, 29.3.3, 30.0.3 or higher.
References
medium severity
- Vulnerable module: got
- Introduced through: nodemon@1.19.4
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › update-notifier@2.5.0 › latest-version@3.1.0 › package-json@4.0.1 › got@6.7.1Remediation: Upgrade to nodemon@2.0.17.
Overview
Affected versions of this package are vulnerable to Open Redirect due to missing verification of requested URLs. It allowed a victim to be redirected to a UNIX socket.
Remediation
Upgrade got to version 11.8.5, 12.1.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation. It is possible to kill a renderer if it provides an unexpected FrameOwnerElementType.
Remediation
Upgrade electron to version 13.5.1, 12.2.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation.
in Internals, due to not treating % as a special character in pathname resolution.
NOTE: This vulnerability is only exploitable when running on Windows.
Remediation
Upgrade electron to version 18.3.8, 19.0.13 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure. IPC messages sent from the main process to a subframe in the renderer process, through webContents.sendToFrame, event.reply or when using the remote module, can in some cases be delivered to the wrong frame.
Remediation
Upgrade electron to version 9.4.0, 10.2.0, 11.1.0, 12.0.0-beta.9 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.1.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure. The is a side-channel information leakage in autofill.
Remediation
Upgrade electron to version 11.4.0, 10.4.1 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@14.2.8.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure where ImageBitmaps that is created by webGL contexts will fail to render.
Remediation
Upgrade electron to version 14.2.8, 15.4.2, 16.2.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.9.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure in Background Fetch, by exposing URLs during cross-origin redirects.
Remediation
Upgrade electron to version 18.3.9, 19.0.12 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.1.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out-of-Bounds. An out of bounds write issue exists in engine.
Remediation
Upgrade electron to version 13.5.0, 12.1.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@29.4.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Type Confusion via a crafted HTML page in the V8 engine.
**Note: ** This is only exploitable if the user navigates to or is redirected to the malicious page.
Remediation
Upgrade electron to version 29.4.3 or higher.
References
medium severity
- Vulnerable module: follow-redirects
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › follow-redirects@1.2.1
Overview
Affected versions of this package are vulnerable to Information Exposure by leaking the cookie header to a third party site in the process of fetching a remote URL with the cookie in the request body. If the response contains a location header, it will follow the redirect to another URL of a potentially malicious actor, to which the cookie would be exposed.
Remediation
Upgrade follow-redirects to version 1.14.7 or higher.
References
medium severity
- Vulnerable module: glob-parent
- Introduced through: nodemon@1.19.4 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › glob-parent@3.1.0Remediation: Upgrade to nodemon@2.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › mqtt@2.2.1 › help-me@1.1.0 › glob-stream@6.1.0 › glob-parent@3.1.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › mqtt@2.18.9 › help-me@1.1.0 › glob-stream@6.1.0 › glob-parent@3.1.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › mqtt@2.18.9 › help-me@1.1.0 › glob-stream@6.1.0 › glob-parent@3.1.0
Overview
glob-parent is a package that helps extracting the non-magic parent path from a glob string.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). The enclosure regex used to check for strings ending in enclosure containing path separator.
PoC by Yeting Li
var globParent = require("glob-parent")
function build_attack(n) {
var ret = "{"
for (var i = 0; i < n; i++) {
ret += "/"
}
return ret;
}
globParent(build_attack(5000));
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade glob-parent to version 5.1.2 or higher.
References
medium severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
POC
var lo = require('lodash');
function build_blank (n) {
var ret = "1"
for (var i = 0; i < n; i++) {
ret += " "
}
return ret + "1";
}
var s = build_blank(50000)
var time0 = Date.now();
lo.trim(s)
var time_cost0 = Date.now() - time0;
console.log("time_cost0: " + time_cost0)
var time1 = Date.now();
lo.toNumber(s)
var time_cost1 = Date.now() - time1;
console.log("time_cost1: " + time_cost1)
var time2 = Date.now();
lo.trimEnd(s)
var time_cost2 = Date.now() - time2;
console.log("time_cost2: " + time_cost2)
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade lodash to version 4.17.21 or higher.
References
medium severity
- Vulnerable module: micromatch
- Introduced through: nodemon@1.19.4
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › nodemon@1.19.4 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10
Overview
Affected versions of this package are vulnerable to Inefficient Regular Expression Complexity due to the use of unsafe pattern configurations that allow greedy matching through the micromatch.braces() function. An attacker can cause the application to hang or slow down by passing a malicious payload that triggers extensive backtracking in regular expression processing.
Remediation
Upgrade micromatch to version 4.0.8 or higher.
References
medium severity
- Vulnerable module: nodemailer
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › nodemailer@1.11.0
Overview
nodemailer is an Easy as cake e-mail sending from your Node.js applications
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the attachDataUrls parameter or when parsing attachments with an embedded file. An attacker can exploit this vulnerability by sending a specially crafted email that triggers inefficient regular expression evaluation, leading to excessive consumption of CPU resources.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade nodemailer to version 6.9.9 or higher.
References
medium severity
- Vulnerable module: uglify-js
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › uglify-js@2.7.5
Overview
uglify-js is a JavaScript parser, minifier, compressor and beautifier toolkit.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the string_template and the decode_template functions.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade uglify-js to version 3.14.3 or higher.
References
medium severity
- Vulnerable module: ws
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › ws@1.1.1Remediation: Open PR to patch ws@1.1.1.
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of the package use the cryptographically insecure Math.random() which can produce predictable values and should not be used in security-sensitive context.
Details
Computers are deterministic machines, and as such are unable to produce true randomness. Pseudo-Random Number Generators (PRNGs) approximate randomness algorithmically, starting with a seed from which subsequent values are calculated.
There are two types of PRNGs: statistical and cryptographic. Statistical PRNGs provide useful statistical properties, but their output is highly predictable and forms an easy to reproduce numeric stream that is unsuitable for use in cases where security depends on generated values being unpredictable. Cryptographic PRNGs address this problem by generating output that is more difficult to predict. For a value to be cryptographically secure, it must be impossible or highly improbable for an attacker to distinguish between it and a truly random value. In general, if a PRNG algorithm is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.
You can read more about node's insecure Math.random() in Mike Malone's post.
Remediation
Upgrade ws to version 1.1.2 or higher.
References
medium severity
- Vulnerable module: ws
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › mqtt@2.2.1 › websocket-stream@3.3.3 › ws@1.1.5
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › ws@1.1.5
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › ws@1.1.5
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › ws@1.1.1
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). A specially crafted value of the Sec-Websocket-Protocol header can be used to significantly slow down a ws server.
##PoC
for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
const value = 'b' + ' '.repeat(length) + 'x';
const start = process.hrtime.bigint();
value.trim().split(/ *, */);
const end = process.hrtime.bigint();
console.log('length = %d, time = %f ns', length, end - start);
}
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade ws to version 7.4.6, 6.2.2, 5.2.3 or higher.
References
medium severity
- Vulnerable module: xml2js
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › xml2js@0.4.17
Overview
Affected versions of this package are vulnerable to Prototype Pollution due to allowing an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the __proto__ property to be edited.
PoC
var parseString = require('xml2js').parseString;
let normal_user_request = "<role>admin</role>";
let malicious_user_request = "<__proto__><role>admin</role></__proto__>";
const update_user = (userProp) => {
// A user cannot alter his role. This way we prevent privilege escalations.
parseString(userProp, function (err, user) {
if(user.hasOwnProperty("role") && user?.role.toLowerCase() === "admin") {
console.log("Unauthorized Action");
} else {
console.log(user?.role[0]);
}
});
}
update_user(normal_user_request);
update_user(malicious_user_request);
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade xml2js to version 0.5.0 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@35.7.5.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Arbitrary Code Injection via modification of the resources folder when the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses are enabled. An attacker can execute unauthorized code by altering files within the application directory, bypassing ASAR integrity checks.
Note: This is only exploitable if the application is launched from a filesystem to which the attacker has write access.
Remediation
Upgrade electron to version 35.7.5, 36.8.1, 37.3.1, 38.0.0-beta.6 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@36.3.0.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Information Exposure via the Loader component. An attacker can leak sensitive cross-origin data by crafting a malicious HTML page.
Remediation
Upgrade electron to version 36.3.0 or higher.
References
medium severity
- Vulnerable module: express
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0
Overview
express is a minimalist web framework.
Affected versions of this package are vulnerable to Cross-site Scripting due to improper handling of user input in the response.redirect method. An attacker can execute arbitrary code by passing malicious input to this method.
Note
To exploit this vulnerability, the following conditions are required:
The attacker should be able to control the input to
response.redirect()express must not redirect before the template appears
the browser must not complete redirection before:
the user must click on the link in the template
Remediation
Upgrade express to version 4.20.0, 5.0.0 or higher.
References
medium severity
- Vulnerable module: request
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › picture-tube@1.0.0 › request@2.9.203Remediation: Open PR to patch request@2.9.203.
Overview
request is a simplified http request client.
Affected versions of this package are vulnerable to Remote Memory Exposure.
A potential remote memory exposure vulnerability exists in request. If a request uses a multipart attachment and the body type option is number with value X, then X bytes of uninitialized memory will be sent in the body of the request.
Note that while the impact of this vulnerability is high (memory exposure), exploiting it is likely difficult, as the attacker needs to somehow control the body type of the request. One potential exploit scenario is when a request is composed based on JSON input, including the body type, allowing a malicious JSON to trigger the memory leak.
Details
Constructing a Buffer class with integer N creates a Buffer
of length N with non zero-ed out memory.
Example:
var x = new Buffer(100); // uninitialized Buffer of length 100
// vs
var x = new Buffer('100'); // initialized Buffer with value of '100'
Initializing a multipart body in such manner will cause uninitialized memory to be sent in the body of the request.
Proof of concept
var http = require('http')
var request = require('request')
http.createServer(function (req, res) {
var data = ''
req.setEncoding('utf8')
req.on('data', function (chunk) {
console.log('data')
data += chunk
})
req.on('end', function () {
// this will print uninitialized memory from the client
console.log('Client sent:\n', data)
})
res.end()
}).listen(8000)
request({
method: 'POST',
uri: 'http://localhost:8000',
multipart: [{ body: 1000 }]
},
function (err, res, body) {
if (err) return console.error('upload failed:', err)
console.log('sent')
})
Remediation
Upgrade request to version 2.68.0 or higher.
References
medium severity
patched
- Vulnerable module: tunnel-agent
- Introduced through: unirest@0.5.1
Vulnerability patched for: unirest request tunnel-agent
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › request@2.74.0 › tunnel-agent@0.4.3Remediation: Upgrade to unirest@0.6.0.
Overview
tunnel-agent is HTTP proxy tunneling agent. Affected versions of the package are vulnerable to Uninitialized Memory Exposure.
A possible memory disclosure vulnerability exists when a value of type number is used to set the proxy.auth option of a request request and results in a possible uninitialized memory exposures in the request body.
This is a result of unobstructed use of the Buffer constructor, whose insecure default constructor increases the odds of memory leakage.
Details
Constructing a Buffer class with integer N creates a Buffer of length N with raw (not "zero-ed") memory.
In the following example, the first call would allocate 100 bytes of memory, while the second example will allocate the memory needed for the string "100":
// uninitialized Buffer of length 100
x = new Buffer(100);
// initialized Buffer with value of '100'
x = new Buffer('100');
tunnel-agent's request construction uses the default Buffer constructor as-is, making it easy to append uninitialized memory to an existing list. If the value of the buffer list is exposed to users, it may expose raw server side memory, potentially holding secrets, private data and code. This is a similar vulnerability to the infamous Heartbleed flaw in OpenSSL.
Proof of concept by ChALkeR
require('request')({
method: 'GET',
uri: 'http://www.example.com',
tunnel: true,
proxy:{
protocol: 'http:',
host:"127.0.0.1",
port:8080,
auth:80
}
});
You can read more about the insecure Buffer behavior on our blog.
Similar vulnerabilities were discovered in request, mongoose, ws and sequelize.
Remediation
Upgrade tunnel-agent to version 0.6.0 or higher.
Note This is vulnerable only for Node <=4
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@9.4.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Use After Free via the Blink component in chromium.
Remediation
Upgrade electron to version 9.4.2, 10.3.1, 11.2.2 or higher.
References
medium severity
- Vulnerable module: i18next
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › i18next@1.10.6
Overview
i18next is an internationalization framework for browser or any other javascript environment (eg. node.js).
Affected versions of this package are vulnerable to Buffer Overflow. It is possible to cause buffer overflow by changing the translation to be recursive.
Remediation
Upgrade i18next to version 19.5.5 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Input Validation due to insufficient data validation that exists in V8.
Remediation
Upgrade electron to version 10.4.4, 12.0.6 or higher.
References
medium severity
- Vulnerable module: i18next
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › i18next@1.10.6
Overview
i18next is an internationalization framework for browser or any other javascript environment (eg. node.js).
Affected versions of this package are vulnerable to Prototype Pollution. This vulnerability relates to the AddResourceBundle API which uses the the deepExtend function (https://github.com/i18next/i18next/blob/master/i18next.js#L361-L370) internally to extend existing translations in a file. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.
PoC
import i18n from "i18next";
i18n.init({
resources: {
en: {
namespace1: {
key: 'hello from namespace 1'
},
namespace2: {
key: 'hello from namespace 2'
}
},
de: {
namespace1: {
key: 'hallo von namespace 1'
},
namespace2: {
key: 'hallo von namespace 2'
}
}
}
});
var malicious_payload = '{"__proto__":{"vulnerable":"Polluted"}}';
i18n.init({ resources: {} });
i18n.addResourceBundle('en', 'namespace1', JSON.parse(malicious_payload)
,true,true);
console.log(i18n.options.resources);
//a newly created empty object has the vulnerable property
console.log({}.vulnerable);
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade i18next to version 19.8.3 or higher.
References
medium severity
- Vulnerable module: passport
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › passport@0.3.2
Overview
passport is a Simple, unobtrusive authentication for Node.js.
Affected versions of this package are vulnerable to Session Fixation. When a user logs in or logs out, the session is regenerated instead of being closed.
Remediation
Upgrade passport to version 0.6.0 or higher.
References
medium severity
- Vulnerable module: node-red
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2
Overview
node-red is a visual tool for Internet of Things.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). node-red has flows to demonstrate the Inject, Debug and Function nodes and multiple flows can be defined. When renaming the flow - malicious javascript can be inserted into the Name field.
Details
Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
Types of attacks
There are a few methods by which XSS can be manipulated:
| Type | Origin | Description |
|---|---|---|
| Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
| Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
| DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
| Mutated | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
Affected environments
The following environments are susceptible to an XSS attack:
- Web servers
- Application servers
- Web application environments
How to prevent
This section describes the top best practices designed to specifically protect your code:
- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as
?,&,/,<,>and spaces to their respective HTML or URL encoded equivalents. - Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
Remediation
Upgrade node-red to version 0.20.7 or higher.
References
medium severity
- Vulnerable module: on-headers
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › on-headers@1.0.1
Overview
Affected versions of this package are vulnerable to Improper Handling of Unexpected Data Type via the response.writeHead function. An attacker can manipulate HTTP response headers by passing an array to this function, potentially leading to unintended disclosure or modification of header information.
Workaround
This vulnerability can be mitigated by passing an object to response.writeHead() instead of an array.
Remediation
Upgrade on-headers to version 1.1.0 or higher.
References
medium severity
- Vulnerable module: lodash
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › node-rsa@0.2.30 › lodash@3.3.0
Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It parses dates using regex strings, which may cause a slowdown of 2 seconds per 50k characters.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade lodash to version 4.17.11 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Exposure of Resource to Wrong Sphere. Inappropriate implementation in Background Fetch API in Google Chrome prior to 94.0.4606.54 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Remediation
Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@12.2.2.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Access Control. Inappropriate implementation in Background Fetch API in Google Chrome prior to 94.0.4606.54 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page.
Remediation
Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@18.3.11.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Authentication by allowing the creation of cookies that have an empty name field and whose value impersonates a cookie name prefix.
Note:
Upgrading to the fixed version will delete any previously stored cookies that meet the conditions by causing them to fail their IsCanonical() check.
Remediation
Upgrade electron to version 18.3.11 or higher.
References
medium severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@15.5.3.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper implementation in Compositing.
Remediation
Upgrade electron to version 15.5.3, 16.2.4 or higher.
References
medium severity
- Vulnerable module: mqtt
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › mqtt@2.2.1
Overview
mqtt is a client library for the MQTT protocol, written in JavaScript for node.js and the browser.
Affected versions of this package are vulnerable to Denial of Service (DoS) attacks. MQTT.js 2.x.x prior to 2.15.0 issue in handling PUBLISH tickets may lead to an attacker causing a denial-of-service condition.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
References
low severity
- Vulnerable module: debug
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › body-parser@1.15.2 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › finalhandler@0.5.0 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › send@0.14.1 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2 › send@0.14.2 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1 › debug@2.2.0Remediation: Open PR to patch debug@2.2.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › debug@2.3.3Remediation: Open PR to patch debug@2.3.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › debug@2.3.3Remediation: Open PR to patch debug@2.3.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › debug@2.3.3Remediation: Open PR to patch debug@2.3.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › debug@2.3.3Remediation: Open PR to patch debug@2.3.3.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › debug@4.1.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › engine.io@3.5.0 › debug@4.1.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0 › socket.io@2.4.1 › socket.io-parser@3.4.3 › debug@4.1.1
Overview
debug is a small debugging utility.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the function useColors via manipulation of the str argument.
The vulnerability can cause a very low impact of about 2 seconds of matching time for data 50k characters long.
Note: CVE-2017-20165 is a duplicate of this vulnerability.
PoC
Use the following regex in the %o formatter.
/\s*\n\s*/
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade debug to version 2.6.9, 3.1.0, 3.2.7, 4.3.1 or higher.
References
low severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@10.4.4.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Out Of Bounds Read. Blit11 would clip the destination rectangle with the destination size but ignore the result. gl::ClipRectangle returns false when the rectangles do not intersect at all, indicating the blit can be skipped.
Remediation
Upgrade electron to version 10.4.4, 11.4.4, 12.0.6 or higher.
References
low severity
- Vulnerable module: mime
- Introduced through: snappy-core@github:snappyrobotics/snappy-core and unirest@0.5.1
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › send@0.14.1 › mime@1.3.4Remediation: Open PR to patch mime@1.3.4.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2 › send@0.14.2 › mime@1.3.4Remediation: Open PR to patch mime@1.3.4.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › unirest@0.5.1 › mime@1.3.6Remediation: Upgrade to unirest@0.6.0.
Overview
mime is a comprehensive, compact MIME type module.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It uses regex the following regex /.*[\.\/\\]/ in its lookup, which can cause a slowdown of 2 seconds for 50k characters.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade mime to version 1.4.1, 2.0.3 or higher.
References
low severity
- Vulnerable module: minimist
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › node-red-node-email@0.1.29 › poplib@0.1.7 › optimist@0.6.1 › minimist@0.0.10
Overview
minimist is a parse argument options module.
Affected versions of this package are vulnerable to Prototype Pollution due to a missing handler to Function.prototype.
Notes:
This vulnerability is a bypass to CVE-2020-7598
The reason for the different CVSS between CVE-2021-44906 to CVE-2020-7598, is that CVE-2020-7598 can pollute objects, while CVE-2021-44906 can pollute only function.
PoC by Snyk
require('minimist')('--_.constructor.constructor.prototype.foo bar'.split(' '));
console.log((function(){}).foo); // bar
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
Unsafe
Objectrecursive mergeProperty definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).
lodash and Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
| Type | Origin | Short description |
|---|---|---|
| Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
| Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
| Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
Application server
Web server
Web browser
How to prevent
Freeze the prototype— use
Object.freeze (Object.prototype).Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.As a best practice use
Mapinstead ofObject.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade minimist to version 0.2.4, 1.2.6 or higher.
References
low severity
- Vulnerable module: moment
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-ros@SnappyRobotics/snappy-ros › rosnodejs@2.2.0 › moment@2.12.0
Overview
moment is a lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It used a regular expression (/[0-9]*['a-z\u00A0-\u05FF\u0700-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF]+|[\u0600-\u06FF\/]+(\s*?[\u0600-\u06FF]+){1,2}/i) in order to parse dates specified as strings. This can cause a very low impact of about 2 seconds matching time for data 50k characters long.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade moment to version 2.19.3 or higher.
References
low severity
- Vulnerable module: ms
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › body-parser@1.15.2 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › send@0.14.1 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › finalhandler@0.5.0 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › send@0.14.1 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2 › send@0.14.2 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › socket.io-parser@2.3.1 › debug@2.2.0 › ms@0.7.1Remediation: Open PR to patch ms@0.7.1.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2 › send@0.14.2 › ms@0.7.2Remediation: Open PR to patch ms@0.7.2.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › debug@2.3.3 › ms@0.7.2Remediation: Open PR to patch ms@0.7.2.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › debug@2.3.3 › ms@0.7.2Remediation: Open PR to patch ms@0.7.2.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › debug@2.3.3 › ms@0.7.2Remediation: Open PR to patch ms@0.7.2.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › socket.io-client@1.7.4 › engine.io-client@1.8.6 › debug@2.3.3 › ms@0.7.2Remediation: Open PR to patch ms@0.7.2.
Overview
ms is a tiny millisecond conversion utility.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to an incomplete fix for previously reported vulnerability npm:ms:20151024. The fix limited the length of accepted input string to 10,000 characters, and turned to be insufficient making it possible to block the event loop for 0.3 seconds (on a typical laptop) with a specially crafted string passed to ms() function.
Proof of concept
ms = require('ms');
ms('1'.repeat(9998) + 'Q') // Takes about ~0.3s
Note: Snyk's patch for this vulnerability limits input length to 100 characters. This new limit was deemed to be a breaking change by the author. Based on user feedback, we believe the risk of breakage is very low, while the value to your security is much greater, and therefore opted to still capture this change in a patch for earlier versions as well. Whenever patching security issues, we always suggest to run tests on your code to validate that nothing has been broken.
For more information on Regular Expression Denial of Service (ReDoS) attacks, go to our blog.
Disclosure Timeline
- Feb 9th, 2017 - Reported the issue to package owner.
- Feb 11th, 2017 - Issue acknowledged by package owner.
- April 12th, 2017 - Fix PR opened by Snyk Security Team.
- May 15th, 2017 - Vulnerability published.
- May 16th, 2017 - Issue fixed and version
2.0.0released. - May 21th, 2017 - Patches released for versions
>=0.7.1, <=1.0.0.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade ms to version 2.0.0 or higher.
References
low severity
- Vulnerable module: tar
- Introduced through: serialport@4.0.7 and snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2Remediation: Upgrade to serialport@6.0.0.
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › meshblu@2.3.2 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-node-serialport@0.4.4 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › bcrypt@1.0.3 › node-pre-gyp@0.6.36 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › firmata@0.15.0 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › snappy-io-nodes@SnappyRobotics/snappy-io-nodes › node-red-contrib-gpio@0.9.2 › johnny-five@0.10.13 › serialport@4.0.7 › node-pre-gyp@0.6.39 › tar-pack@3.4.1 › tar@2.2.2
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). When stripping the trailing slash from files arguments, the f.replace(/\/+$/, '') performance of this function can exponentially degrade when f contains many / characters resulting in ReDoS.
This vulnerability is not likely to be exploitable as it requires that the untrusted input is being passed into the tar.extract() or tar.list() array of entries to parse/extract, which would be unusual.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade tar to version 6.1.4, 5.0.8, 4.4.16 or higher.
References
low severity
- Vulnerable module: node-red-dashboard
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red-dashboard@2.30.0
Overview
node-red-dashboard is a provides a set of nodes in Node-RED to quickly create a live data dashboard.
Affected versions of this package are vulnerable to Improper Neutralization due to improper user-input sanitization in ui-component-ctrl.js file, via ui_text format input.
Remediation
Upgrade node-red-dashboard to version 3.2.0 or higher.
References
low severity
- Vulnerable module: electron
- Introduced through: electron@1.8.8
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › electron@1.8.8Remediation: Upgrade to electron@13.6.6.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Access Control via the web Bluetooth API, if the app has not configured a custom select-bluetooth-device event handler.
The device that is accessed is random and the attacker would have no way of selecting a specific device.
Workarounds:
Adding this code to your app can workaround the issue.
app.on('web-contents-created', (event, webContents) => {
webContents.on('select-bluetooth-device', (event, devices, callback) => {
// Prevent default behavior
event.preventDefault();
// Cancel the request
callback('');
});
});
Remediation
Upgrade electron to version 13.6.6, 14.2.4, 15.3.5, 16.0.6, 17.0.0-alpha.6 or higher.
References
low severity
- Vulnerable module: follow-redirects
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › follow-redirects@1.2.1
Overview
Affected versions of this package are vulnerable to Information Exposure due a leakage of the Authorization header from the same hostname during HTTPS to HTTP redirection. An attacker who can listen in on the wire (or perform a MITM attack) will be able to receive the Authorization header due to the usage of the insecure HTTP protocol which does not verify the hostname the request is sending to.
Remediation
Upgrade follow-redirects to version 1.14.8 or higher.
References
low severity
- Vulnerable module: send
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › send@0.14.1
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2 › send@0.14.2
Overview
send is a Better streaming static file server with Range and conditional-GET support
Affected versions of this package are vulnerable to Cross-site Scripting due to improper user input sanitization passed to the SendStream.redirect() function, which executes untrusted code. An attacker can execute arbitrary code by manipulating the input parameters to this method.
Note:
Exploiting this vulnerability requires the following:
The attacker needs to control the input to
response.redirect()Express MUST NOT redirect before the template appears
The browser MUST NOT complete redirection before
The user MUST click on the link in the template
Details
Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
Types of attacks
There are a few methods by which XSS can be manipulated:
| Type | Origin | Description |
|---|---|---|
| Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
| Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
| DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
| Mutated | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
Affected environments
The following environments are susceptible to an XSS attack:
- Web servers
- Application servers
- Web application environments
How to prevent
This section describes the top best practices designed to specifically protect your code:
- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as
?,&,/,<,>and spaces to their respective HTML or URL encoded equivalents. - Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
Remediation
Upgrade send to version 0.19.0, 1.1.0 or higher.
References
low severity
- Vulnerable module: serve-static
- Introduced through: snappy-core@github:snappyrobotics/snappy-core
Detailed paths
-
Introduced through: snappy-gui@snappyrobotics/snappy-gui#0a4cc2dbeea7a51a95f9c96eec35e589d75a66b4 › snappy-core@github:snappyrobotics/snappy-core › node-red@0.16.2 › express@4.14.0 › serve-static@1.11.2
Overview
serve-static is a server.
Affected versions of this package are vulnerable to Cross-site Scripting due to improper sanitization of user input in the redirect function. An attacker can manipulate the redirection process by injecting malicious code into the input.
Note
To exploit this vulnerability, the following conditions are required:
The attacker should be able to control the input to
response.redirect()express must not redirect before the template appears
the browser must not complete redirection before:
the user must click on the link in the template
Details
Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
Types of attacks
There are a few methods by which XSS can be manipulated:
| Type | Origin | Description |
|---|---|---|
| Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
| Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
| DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
| Mutated | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
Affected environments
The following environments are susceptible to an XSS attack:
- Web servers
- Application servers
- Web application environments
How to prevent
This section describes the top best practices designed to specifically protect your code:
- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as
?,&,/,<,>and spaces to their respective HTML or URL encoded equivalents. - Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
Remediation
Upgrade serve-static to version 1.16.0, 2.1.0 or higher.