Vulnerabilities |
10 via 19 paths |
---|---|
Dependencies |
141 |
Source |
npm |
Find, fix and prevent vulnerabilities in your code.
high severity
- Vulnerable module: xmlhttprequest-ssl
- Introduced through: socket.io-client@2.0.3 and socket.io@2.0.3
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io-client@2.0.3 › engine.io-client@3.1.6 › xmlhttprequest-ssl@1.5.5Remediation: Upgrade to fcoin@1.1.0.
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › socket.io-client@2.0.4 › engine.io-client@3.1.6 › xmlhttprequest-ssl@1.5.5Remediation: Upgrade to fcoin@1.1.0.
Overview
xmlhttprequest-ssl is a fork of xmlhttprequest
.
Affected versions of this package are vulnerable to Arbitrary Code Injection. Provided requests are sent synchronously (async=False
on xhr.open
), malicious user input flowing into xhr.send
could result in arbitrary code being injected and run.
POC
const { XMLHttpRequest } = require("xmlhttprequest")
const xhr = new XMLHttpRequest()
xhr.open("POST", "http://localhost.invalid/", false /* use synchronize request */)
xhr.send("\\');require(\"fs\").writeFileSync(\"/tmp/aaaaa.txt\", \"poc-20210306\");req.end();//")
Remediation
Upgrade xmlhttprequest-ssl
to version 1.6.2 or higher.
References
high severity
- Vulnerable module: elliptic
- Introduced through: elliptic@6.4.0
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › elliptic@6.4.0Remediation: Upgrade to fcoin@1.1.0.
Overview
elliptic is a Fast elliptic-curve cryptography in a plain javascript implementation.
Affected versions of this package are vulnerable to Cryptographic Issues. Elliptic allows ECDSA signature malleability via variations in encoding, leading \0
bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
PoC
var crypto = require('crypto')
var EC = require('elliptic').ec;
var ec = new EC('secp256k1');
var obj = require("./poc_ecdsa_secp256k1_sha256_test.json");
for (let testGroup of obj.testGroups) {
var key = ec.keyFromPublic(testGroup.key.uncompressed, 'hex');
for(let test of testGroup.tests) {
console.log("[*] Test " + test.tcId + " result: " + test.result)
msgHash = crypto.createHash('sha256').update(Buffer.from(test.msg, 'hex')).digest();
try {
result = key.verify(msgHash, Buffer.from(test.sig, 'hex'));
if (result == true) {
if (test.result == "valid" || test.result == "acceptable")
console.log("Result: PASS");
else
console.log("Result: FAIL")
}
if (result == false) {
if (test.result == "valid" || test.result == "acceptable")
console.log("Result: FAIL");
else
console.log("Result: PASS")
}
} catch (e) {
console.log("ERROR - VERIFY: " + e)
if (test.result == "valid" || test.result == "acceptable")
console.log("Result: FAIL");
else
console.log("Result: PASS")
}
}
}
Remediation
Upgrade elliptic
to version 6.5.3 or higher.
References
high severity
- Vulnerable module: ansi-regex
- Introduced through: leveldown@1.7.2 and secp256k1@3.3.0
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › leveldown@1.7.2 › prebuild-install@2.5.3 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: fcoin@1.0.0-beta.26 › secp256k1@3.3.0 › prebuild-install@2.5.3 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: fcoin@1.0.0-beta.26 › leveldown@1.7.2 › prebuild-install@2.5.3 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: fcoin@1.0.0-beta.26 › secp256k1@3.3.0 › prebuild-install@2.5.3 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to the sub-patterns [[\\]()#;?]*
and (?:;[-a-zA-Z\\d\\/#&.:=?%@~_]*)*
.
PoC
import ansiRegex from 'ansi-regex';
for(var i = 1; i <= 50000; i++) {
var time = Date.now();
var attack_str = "\u001B["+";".repeat(i*10000);
ansiRegex().test(attack_str)
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:
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 ansi-regex
to version 4.1.1, 5.0.1, 6.0.1 or higher.
References
high severity
- Vulnerable module: engine.io
- Introduced through: socket.io@2.0.3
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › engine.io@3.1.5Remediation: Upgrade to fcoin@1.1.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: socket.io-parser
- Introduced through: socket.io@2.0.3 and socket.io-client@2.0.3
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › socket.io-parser@3.1.3Remediation: Upgrade to fcoin@1.1.0.
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io-client@2.0.3 › socket.io-parser@3.1.3Remediation: Upgrade to fcoin@1.1.0.
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › socket.io-client@2.0.4 › socket.io-parser@3.1.3Remediation: Upgrade to fcoin@1.1.0.
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
ws
package
Remediation
Upgrade socket.io-parser
to version 3.3.2, 3.4.1 or higher.
References
high severity
- Vulnerable module: xmlhttprequest-ssl
- Introduced through: socket.io-client@2.0.3 and socket.io@2.0.3
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io-client@2.0.3 › engine.io-client@3.1.6 › xmlhttprequest-ssl@1.5.5Remediation: Upgrade to fcoin@1.1.0.
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › socket.io-client@2.0.4 › engine.io-client@3.1.6 › xmlhttprequest-ssl@1.5.5Remediation: Upgrade to fcoin@1.1.0.
Overview
xmlhttprequest-ssl is a fork of xmlhttprequest
.
Affected versions of this package are vulnerable to Access Restriction Bypass. The package disables SSL certificate validation by default, because rejectUnauthorized
(when the property exists but is undefined) is considered to be false within the https.request
function of Node.js. In other words, no certificate is ever rejected.
PoC
const XMLHttpRequest = require('xmlhttprequest-ssl');
var xhr = new XMLHttpRequest(); /* pass empty object in version 1.5.4 to work around bug */
xhr.open("GET", "https://self-signed.badssl.com/");
xhr.addEventListener('readystatechange', () => console.log('ready state:', xhr.status));
xhr.addEventListener('loadend', loadend);
function loadend()
{
console.log('loadend:', xhr);
if (xhr.status === 0 && xhr.statusText.code === 'DEPTH_ZERO_SELF_SIGNED_CERT')
console.log('test passed: self-signed cert rejected');
else
console.log('*** test failed: self-signed cert used to retrieve content');
}
xhr.send();
Remediation
Upgrade xmlhttprequest-ssl
to version 1.6.1 or higher.
References
medium severity
- Vulnerable module: elliptic
- Introduced through: elliptic@6.4.0
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › elliptic@6.4.0Remediation: Upgrade to fcoin@1.1.0.
Overview
elliptic is a Fast elliptic-curve cryptography in a plain javascript implementation.
Affected versions of this package are vulnerable to Cryptographic Issues via the secp256k1
implementation in elliptic/ec/key.js
. There is no check to confirm that the public key point passed into the derive function actually exists on the secp256k1
curve. This results in the potential for the private key used in this implementation to be revealed after a number of ECDH operations are performed.
Remediation
Upgrade elliptic
to version 6.5.4 or higher.
References
medium severity
- Vulnerable module: elliptic
- Introduced through: elliptic@6.4.0
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › elliptic@6.4.0Remediation: Upgrade to fcoin@1.1.0.
Overview
elliptic is a Fast elliptic-curve cryptography in a plain javascript implementation.
Affected versions of this package are vulnerable to Timing Attack. Practical recovery of the long-term private key generated by the library is possible under certain conditions. Leakage of bit-length of a scalar during scalar multiplication is possible on an elliptic curve which might allow practical recovery of the long-term private key.
Remediation
Upgrade elliptic
to version 6.5.2 or higher.
References
medium severity
- Vulnerable module: socket.io
- Introduced through: socket.io@2.0.3
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3Remediation: Upgrade to fcoin@1.1.0.
Overview
socket.io is a node.js realtime framework server.
Affected versions of this package are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.
Remediation
Upgrade socket.io
to version 2.4.0 or higher.
References
medium severity
- Vulnerable module: ws
- Introduced through: socket.io@2.0.3 and socket.io-client@2.0.3
Detailed paths
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › engine.io@3.1.5 › ws@3.3.3Remediation: Upgrade to fcoin@1.1.0.
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io-client@2.0.3 › engine.io-client@3.1.6 › ws@3.3.3Remediation: Upgrade to fcoin@1.1.0.
-
Introduced through: fcoin@1.0.0-beta.26 › socket.io@2.0.3 › socket.io-client@2.0.4 › engine.io-client@3.1.6 › ws@3.3.3Remediation: Upgrade to fcoin@1.1.0.
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:
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 ws
to version 7.4.6, 6.2.2, 5.2.3 or higher.