In TypeStack class-validat, validate() input validation can be bypassed because certain internal attributes can be overwritten via a conflicting name. Even though there is an optional forbidUnknownValues parameter that can be used to reduce the risk of this bypass, this option is not documented and thus most developers configure input validation in the vulnerable default manner. With this vulnerability, attackers can launch SQL Injection or XSS attacks by injecting arbitrary malicious input. NOTE: a software maintainer agrees with the "is not documented" finding but suggests that much of the responsibility for the risk lies in a different product.
LösungUnfortunately, there is no solution available yet.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
class-validator:0.13.1Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
LösungUpgrade to version 1.2.6 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
minimist:1.2.5pdfmake is an open source client/server side PDF printing in pure JavaScript. In versions up to and including 0.2.5 pdfmake contains an unsafe evaluation of user controlled input. Users of pdfmake are thus subject to arbitrary code execution in the context of the process running the pdfmake code. There are no known fixes for this issue. Users are advised to restrict access to trusted user input.
LösungUpgrade to version 0.2.6 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
pdfmake:0.2.5Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository eventsource/eventsource prior to v2.0.2.
LösungUpgrade to versions 1.1.1, 2.0.2 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
eventsource:1.1.0Attackers could trick execa into executing arbitrary binaries. This behaviour is caused by the setting `preferLocal=true` which makes execa search for locally installed binaries and executes them. This vulnerability is usually only exploitable when using execa on a client-side LOCAL application.
LösungUpgrade to version 2.0.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
execa:1.0.0Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils 2.0.0 via the name variable in parseQuery.js.
LösungUpgrade to versions 1.4.1, 2.0.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
loader-utils:2.0.0Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils 2.0.0 via the name variable in parseQuery.js.
LösungUpgrade to versions 1.4.1, 2.0.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
loader-utils:1.4.0Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
LösungUpgrade to version 1.2.6 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
minimist:1.2.5pdfmake is an open source client/server side PDF printing in pure JavaScript. In versions up to and including 0.2.5 pdfmake contains an unsafe evaluation of user controlled input. Users of pdfmake are thus subject to arbitrary code execution in the context of the process running the pdfmake code. There are no known fixes for this issue. Users are advised to restrict access to trusted user input.
LösungUpgrade to version 0.2.6 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
pdfmake:0.2.2Due to improper type validation in attachment parsing the Socket.io js library, it is possible to overwrite the _placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object.
LösungUpgrade to versions 4.0.5, 4.2.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
socket.io-parser:4.0.4This affects all versions of package dicer. A malicious attacker can send a modified form to server, and crash the nodejs service. An attacker could sent the payload again and again so that the service continuously crashes.
LösungUnfortunately, there is no solution available yet.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
dicer:0.2.5qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. 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. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
LösungUpgrade to version 4.17.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
express:4.17.1A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
LösungUpgrade to version 3.0.5 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
minimatch:3.0.4qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. 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. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
LösungUpgrade to versions 6.2.4, 6.3.3, 6.8.3, 6.9.7, 6.10.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
qs:6.7.0qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. 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. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
LösungUpgrade to versions 6.2.4, 6.3.3, 6.8.3, 6.9.7, 6.10.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
qs:6.10.1The package terser before 4.8.1, from 5.0.0 and before 5.14.2 is vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.
LösungUpgrade to versions 4.8.1, 5.14.2 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
terser:5.9.0This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.
LösungUpgrade to version 0.0.8 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
ansi-html:0.0.7A vulnerability exists in Async through 3.2.1 (fixed in 3.2.2), which could let a malicious user obtain privileges via the mapValues() method.
LösungUpgrade to versions 2.6.4, 3.2.2 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
async:2.6.3Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
LösungUpgrade to versions 4.1.2, 5.2.1, 6.1.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
engine.io:4.1.1qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. 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. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
LösungUpgrade to version 4.17.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
express:4.17.1A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
LösungUpgrade to versions 1.4.2, 2.0.4, 3.2.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
loader-utils:1.4.0A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
LösungUpgrade to versions 1.4.2, 2.0.4, 3.2.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
loader-utils:2.0.0A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in `interpolateName.js`.
LösungUpgrade to versions 1.4.2, 2.0.4, 3.2.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
loader-utils:2.0.0A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in `interpolateName.js`.
LösungUpgrade to versions 1.4.2, 2.0.4, 3.2.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
loader-utils:1.4.0The regular expression `block.def` may cause catastrophic backtracking against some strings and lead to a regular expression denial of service (ReDoS). Anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected. This issue is patched As a workaround, avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
LösungUpgrade to version 4.0.10 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
marked:2.1.3The regular expression `inline.reflinkSearch` may cause catastrophic backtracking against some strings and lead to a denial of service (DoS). Anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected. This issue is patched As a workaround, avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
LösungUpgrade to version 4.0.10 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
marked:2.1.3A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
LösungUpgrade to version 3.0.5 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
minimatch:3.0.4qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. 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. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
LösungUpgrade to versions 6.2.4, 6.3.3, 6.8.3, 6.9.7, 6.10.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
qs:6.7.0qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. 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. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
LösungUpgrade to versions 6.2.4, 6.3.3, 6.8.3, 6.9.7, 6.10.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
qs:6.5.2The package terser before 4.8.1, from 5.0.0 and before 5.14.2 is vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.
LösungUpgrade to versions 4.8.1, 5.14.2 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
terser:5.7.0Due to improper authorization, Red Hat Single Sign-On is vulnerable to users performing actions that they should not be allowed to perform. It was possible to add users to the master realm even though no respective permission was granted.
LösungUpgrade to version 17.0.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
keycloak-connect:15.0.2Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the engine.io package, including those who uses depending packages like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
LösungUpgrade to versions 3.6.1, 6.2.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
engine.io:4.1.1The package karma before 6.3.16 is vulnerable to Open Redirect due to missing validation of the return_url query parameter.
LösungUpgrade to version 6.3.16 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
karma:6.3.4log4js-node is a port of log4js to node. fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config. Users are advised to update.
LösungUpgrade to version 6.4.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
log4js:6.3.0The package nanoid is vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.
LösungUpgrade to version 3.1.31 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
nanoid:3.1.23Output from the synchronous version of `shell.exec()` may be visible to other users on the same system. You may be affected if you execute `shell.exec()` in multi-user Mac, Linux, or WSL environments, or if you execute `shell.exec()` as the root user. Other shelljs functions (including the asynchronous version of `shell.exec()`) are not impacted.
LösungUpgrade to version 0.8.5 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
shelljs:0.8.4The swagger-ui-dist package before 4.1.3 for Node.js could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim.
LösungUpgrade to version 4.1.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
swagger-ui-dist:3.52.0Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in swagger-ui-dist.
LösungUpgrade to version 4.1.3 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
swagger-ui-dist:3.52.0### Impact Versions of `validator` prior to 13.7.0 are affected by an inefficient Regular Expression complexity when using the `rtrim` and `trim` sanitizers. ### Patches The problem has been patched in validator 13.7.0
LösungUpgrade to version 13.7.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
validator:13.6.0glob-parent before 6.0.1 and 5.1.2 is vulnerable to Regular Expression Denial of Service (ReDoS). This issue is fixed in version 6.0.1 and 5.1.2.
LösungUpgrade to versions 5.1.2, 6.0.1 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
glob-parent:3.1.0Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not properly check `DigestInfo` for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
LösungUpgrade to version 1.3.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
node-forge:0.10.0### Impact The `forge.debug` API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way. ### Patches The `forge.debug` API and related functions were removed in 1.0.0. ### Workarounds Don't use the `forge.debug` API directly or indirectly with untrusted input. ### References - https://www.huntr.dev/bounties/1-npm-node-forge/ ### For more information If you have any questions or comments about this advisory: * Open an issue in [forge](https://github.com/digitalbazaar/forge). * Email us at support@digitalbazaar.com.
LösungUpgrade to version 1.0.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
node-forge:0.10.0Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
LösungUpgrade to version 1.3.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
node-forge:0.10.0Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a `DigestInfo` ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
LösungUpgrade to version 1.3.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
node-forge:0.10.0### Impact The regex used for the `forge.util.parseUrl` API would not properly parse certain inputs resulting in a parsed data structure that could lead to undesired behavior. ### Patches `forge.util.parseUrl` and other very old related URL APIs were removed in 1.0.0 in favor of letting applications use the more modern WHATWG URL Standard API. ### Workarounds Ensure code does not directly or indirectly call `forge.util.parseUrl` with untrusted input. ### References - https://www.huntr.dev/bounties/41852c50-3c6d-4703-8c55-4db27164a4ae/ ### For more information If you have any questions or comments about this advisory: * Open an issue in [forge](https://github.com/digitalbazaar/forge) * Email us at support@digitalbazaar.com
LösungUpgrade to version 1.0.0 or above.
IdentifikatorenDetailsScanner:
GemnasiumVulnerable Package:
node-forge:0.10.0