Find, fix and prevent vulnerabilities in your code.
high severity
- Vulnerable module: pug
- Introduced through: pug@2.0.4
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › pug@2.0.4Remediation: Upgrade to pug@3.0.1.
Overview
pug is an A clean, whitespace-sensitive template language for writing HTML
Affected versions of this package are vulnerable to Remote Code Execution (RCE). If a remote attacker was able to control the pretty option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.
Remediation
Upgrade pug
to version 3.0.1 or higher.
References
high severity
- Vulnerable module: engine.io
- Introduced through: socket.io@2.5.0
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › socket.io@2.5.0 › engine.io@3.6.1Remediation: Upgrade to socket.io@3.0.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
ws
package
Remediation
Upgrade engine.io
to version 4.0.0 or higher.
References
high severity
- Vulnerable module: jpeg-js
- Introduced through: jimp@0.9.8
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › jimp@0.9.8 › @jimp/types@0.9.8 › @jimp/jpeg@0.9.8 › jpeg-js@0.3.7Remediation: Upgrade to jimp@0.12.0.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS) where a particular piece of input will cause to enter an infinite loop and never return.
PoC
- Create a npm workspace
npm init
- Install the
jpeg-js
library - Create a JS file with the following code:
const jpeg = require('jpeg-js');
let buf = Buffer.from( 'ffd8ffc1f151d800ff51d800ffdaffde', 'hex' );
jpeg.decode( buf );
- Run the file and observe that the code never stops running
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
ws
package
Remediation
Upgrade jpeg-js
to version 0.4.4 or higher.
References
medium severity
- Vulnerable module: jpeg-js
- Introduced through: jimp@0.9.8
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › jimp@0.9.8 › @jimp/types@0.9.8 › @jimp/jpeg@0.9.8 › jpeg-js@0.3.7Remediation: Upgrade to jimp@0.12.0.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS). The attacker could manipulate the exif data in the image file such as change the image pixel to 64250x64250pixels. If the module loaded the crafted image, it tries to allocate 4128062500 pixels into memory.
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
ws
package
Remediation
Upgrade jpeg-js
to version 0.4.0 or higher.
References
medium severity
- Vulnerable module: uglify-js
- Introduced through: pug@2.0.4
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › pug@2.0.4 › pug-filters@3.1.1 › uglify-js@2.8.29Remediation: Upgrade to pug@3.0.0.
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:
A
The 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.D
Finally, 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
new
- Vulnerable module: phin
- Introduced through: jimp@0.9.8
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › jimp@0.9.8 › @jimp/custom@0.9.8 › @jimp/core@0.9.8 › phin@2.9.3Remediation: Upgrade to jimp@0.22.0.
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › jimp@0.9.8 › @jimp/custom@0.9.8 › @jimp/core@0.9.8 › load-bmfont@1.4.1 › phin@2.9.3
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › jimp@0.9.8 › @jimp/plugins@0.9.8 › @jimp/plugin-print@0.9.8 › load-bmfont@1.4.1 › phin@2.9.3
Overview
phin is a The ultra-lightweight Node.js HTTP client
Affected versions of this package are vulnerable to Information Exposure Through Sent Data due to the handling of HTTP headers during redirects when followRedirects
is enabled. An attacker can potentially intercept sensitive information by exploiting how headers are included in outgoing requests after a redirect.
Remediation
Upgrade phin
to version 3.7.1 or higher.
References
low severity
- Vulnerable module: debug
- Introduced through: socket.io@2.5.0
Detailed paths
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › socket.io@2.5.0 › debug@4.1.1Remediation: Upgrade to socket.io@3.0.5.
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › socket.io@2.5.0 › engine.io@3.6.1 › debug@4.1.1Remediation: Upgrade to socket.io@3.0.0.
-
Introduced through: conet_client@qtgate/qtgate-desktop-client#e1c9b7b42009f4dc31030eb6b56855e0d561a91f › socket.io@2.5.0 › socket.io-parser@3.4.3 › debug@4.1.1Remediation: Upgrade to socket.io@3.0.0.
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:
A
The 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.D
Finally, 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.