Vulnerabilities

 20 via 20 paths

Dependencies

 136

Source

 GitHub

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 7
  • 13
Status
  • 20
  • 0
  • 0

high severity

Inefficient Algorithmic Complexity

  • Vulnerable module: linkify-it
  • Introduced through: jsdoc@3.6.11

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsdoc@3.6.11 › markdown-it@12.3.2 › linkify-it@3.0.3
    Remediation: Upgrade to jsdoc@4.0.3.

Overview

linkify-it is a Links recognition library with FULL unicode support

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in the mailto: validator scan-loop on attacker-supplied text. An attacker can cause excessive CPU consumption by submitting specially crafted input that triggers repeated scanning of the remaining text.

Remediation

Upgrade linkify-it to version 5.0.2 or higher.

References

Inefficient Algorithmic Complexity vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: linkify-it
  • Introduced through: jsdoc@3.6.11

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsdoc@3.6.11 › markdown-it@12.3.2 › linkify-it@3.0.3
    Remediation: Upgrade to jsdoc@4.0.3.

Overview

linkify-it is a Links recognition library with FULL unicode support

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to quadratic algorithmic complexity in the match function. An attacker can exhaust CPU resources and cause significant delays in processing by submitting specially crafted input containing a large number of email-like or link-like strings.

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. 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 linkify-it to version 5.0.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: qs
  • Introduced through: body-parser@1.18.2

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › body-parser@1.18.2 › qs@6.5.1
    Remediation: Upgrade to body-parser@1.20.4.

Overview

qs is a querystring parser that supports nesting and arrays, with a depth limit.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via improper enforcement of the arrayLimit option in bracket notation parsing. An attacker can exhaust server memory and cause application unavailability by submitting a large number of bracket notation parameters - like a[]=1&a[]=2 - in a single HTTP request.

PoC


const qs = require('qs');
const attack = 'a[]=' + Array(10000).fill('x').join('&a[]=');
const result = qs.parse(attack, { arrayLimit: 100 });
console.log(result.a.length);  // Output: 10000 (should be max 100)

Remediation

Upgrade qs to version 6.14.1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Asymmetric Resource Consumption (Amplification)

  • Vulnerable module: body-parser
  • Introduced through: body-parser@1.18.2

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › body-parser@1.18.2
    Remediation: Upgrade to body-parser@1.20.3.

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

Asymmetric Resource Consumption (Amplification) vulnerability report

high severity

Infinite loop

  • Vulnerable module: markdown-it
  • Introduced through: jsdoc@3.6.11

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsdoc@3.6.11 › markdown-it@12.3.2
    Remediation: Upgrade to jsdoc@4.0.3.

Overview

markdown-it is a modern pluggable markdown parser.

Affected versions of this package are vulnerable to Infinite loop in linkify inline rule when using malformed input.

Remediation

Upgrade markdown-it to version 13.0.2 or higher.

References

Infinite loop vulnerability report

high severity

Prototype Poisoning

  • Vulnerable module: qs
  • Introduced through: body-parser@1.18.2

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › body-parser@1.18.2 › qs@6.5.1
    Remediation: Upgrade to body-parser@1.19.2.

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 ws package

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

Prototype Poisoning vulnerability report

high severity

Internal Property Tampering

  • Vulnerable module: taffydb
  • Introduced through: jsdoc@3.6.11

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsdoc@3.6.11 › taffydb@2.6.2

Overview

taffydb is an open source JavaScript library that provides in-memory database capabilities

Affected versions of this package are vulnerable to Internal Property Tampering. taffy sets an internal index for each data item in its DB. However, it is found that the internal index can be forged by adding additional properties into user-input. If an index is found in the query, taffyDB will ignore other query conditions and directly return the indexed data item. Moreover, the internal index is in an easily-guessable format (e.g. T000002R000001). As such, attackers can use this vulnerability to access any data items in the DB and exploit an SQL Injection.

Note: The taffy package has been deprecated by the author. Its successor package, taffydb, is also found to be vulnerable and is not actively maintained.

PoC

var TAFFY = require('taffy');
var friends = TAFFY([
        {"id":1,"gender":"M","username":"Smith","password":"aaa","status":"Active"},
        {"id":2,"gender":"F","username":"Ruth","password":"bbb","status":"Active"},
        {"id":3,"gender":"M","username":"Stevenson","password":"ccc","status":"Active"},
        {"id":4,"gender":"F","username":"Gill","password":"ddd","status":"Active"}
]);

var json = {username:"Smith", "password":"123", "___id":"T000002R000002", "___s":true};
var item1 = friends(json);
console.log(item1.first());

Remediation

There is no fixed version for taffydb.

References

Internal Property Tampering vulnerability report

medium severity

Inefficient Algorithmic Complexity

  • Vulnerable module: markdown-it
  • Introduced through: jsdoc@3.6.11

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsdoc@3.6.11 › markdown-it@12.3.2
    Remediation: Upgrade to jsdoc@4.0.3.

Overview

markdown-it is a modern pluggable markdown parser.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity through the replaceAt() function in the smartquotes rule when processing markdown input with a large number of consecutive quotation marks and the typographer option enabled. An attacker can cause excessive CPU consumption and disrupt service availability by submitting specially crafted markdown content containing many quote characters.

Remediation

Upgrade markdown-it to version 14.2.0 or higher.

References

Inefficient Algorithmic Complexity vulnerability report

medium severity

Improper Output Neutralization for Logs

  • Vulnerable module: morgan
  • Introduced through: morgan@1.9.0

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › morgan@1.9.0
    Remediation: Upgrade to morgan@1.11.0.

Overview

morgan is a HTTP request logger middleware for node.js.

Affected versions of this package are vulnerable to Improper Output Neutralization for Logs via the :remote-user token, which extracts the Basic auth username from the Authorization header and writes it to the log stream without neutralizing control characters. An attacker can inject forged log lines by sending crafted Authorization headers containing CR or LF bytes, potentially breaking the one-request-per-line structure of access logs and misleading downstream log consumers.

Workaround

This vulnerability can be mitigated by using a custom format string that does not include :remote-user.

Remediation

Upgrade morgan to version 1.11.0 or higher.

References

Improper Output Neutralization for Logs vulnerability report

medium severity

Improper Output Neutralization for Logs

  • Vulnerable module: morgan
  • Introduced through: morgan@1.9.0

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › morgan@1.9.0
    Remediation: Upgrade to morgan@1.12.0.

Overview

morgan is a HTTP request logger middleware for node.js.

Affected versions of this package are vulnerable to Improper Output Neutralization for Logs in its format-token expansion, which does not neutralize the Unicode line separators U+0085 (NEL), U+2028 (LINE SEPARATOR), and U+2029 (PARAGRAPH SEPARATOR) in logged fields such as :url, :user-agent, :referrer, :req[header], and :remote-user, unlike the earlier fix that escaped C0 control characters. An attacker can forge additional log records by sending ordinary HTTP request headers or a request URL containing these characters, which Unicode-aware downstream log processors interpret as line breaks and split into separate entries. Exploitation requires the downstream log analysis tooling to treat these code points as record separators, and all built-in formats (combined, common, default, and short) are affected.

Note: This is a bypass of the fix for the vulnerability described in CVE-2026-5078.

Remediation

Upgrade morgan to version 1.12.0 or higher.

References

Improper Output Neutralization for Logs vulnerability report

medium severity
new

Improper Output Neutralization for Logs

  • Vulnerable module: morgan
  • Introduced through: morgan@1.9.0

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › morgan@1.9.0
    Remediation: Upgrade to morgan@1.12.1.

Overview

morgan is a HTTP request logger middleware for node.js.

Affected versions of this package are vulnerable to Improper Output Neutralization for Logs via the escapeLogField function. An attacker can manipulate log entries by injecting unescaped double quotes into HTTP headers such as User-Agent or Referer, causing log consumers that parse logs by field position to misinterpret attacker-supplied data as subsequent fields.

Remediation

Upgrade morgan to version 1.12.1 or higher.

References

Improper Output Neutralization for Logs vulnerability report

medium severity

Uncaught Exception

  • Vulnerable module: qs
  • Introduced through: body-parser@1.18.2

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › body-parser@1.18.2 › qs@6.5.1
    Remediation: Upgrade to body-parser@1.20.8.

Overview

qs is a querystring parser that supports nesting and arrays, with a depth limit.

Affected versions of this package are vulnerable to Uncaught Exception in the isBuffer() function in lib/utils.js, which calls obj.constructor.isBuffer(obj) without checking that it is callable, reached from stringify() at lib/stringify.js:127. An attacker can throw an uncaught TypeError that fails each request with HTTP 500, and terminates the worker process when stringify() runs in an unguarded async context, by supplying a query string such as x[constructor][isBuffer]=y that sets constructor.isBuffer to a non-function value. This requires the application to call qs.parse() with plainObjects: true or allowPrototypes: true, which preserves the constructor own property, and to then pass the parsed result to qs.stringify().

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 qs to version 6.16.0 or higher.

References

Uncaught Exception vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: jsonwebtoken
  • Introduced through: jsonwebtoken@8.5.1

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsonwebtoken@8.5.1
    Remediation: Upgrade to jsonwebtoken@9.0.0.

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

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Arbitrary Code Injection

  • Vulnerable module: morgan
  • Introduced through: morgan@1.9.0

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › morgan@1.9.0
    Remediation: Upgrade to morgan@1.9.1.

Overview

morgan is a HTTP request logger middleware for node.js.

Affected versions of this package are vulnerable to Arbitrary Code Injection. An attacker could use the format parameter to inject arbitrary commands.

Remediation

Upgrade morgan to version 1.9.1 or higher.

References

Arbitrary Code Injection vulnerability report

medium severity

Improper Restriction of Security Token Assignment

  • Vulnerable module: jsonwebtoken
  • Introduced through: jsonwebtoken@8.5.1

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsonwebtoken@8.5.1
    Remediation: Upgrade to jsonwebtoken@9.0.0.

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

Improper Restriction of Security Token Assignment vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: jsonwebtoken
  • Introduced through: jsonwebtoken@8.5.1

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsonwebtoken@8.5.1
    Remediation: Upgrade to jsonwebtoken@9.0.0.

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:

  1. A token with no signature is received.

  2. No algorithms are specified.

  3. A falsy (e.g., null, false, undefined) secret or key is passed.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

Improper Authentication vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: body-parser
  • Introduced through: body-parser@1.18.2

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › body-parser@1.18.2
    Remediation: Upgrade to body-parser@1.20.6.

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to invalid limit option handling in normalizeOptions in lib/utils.js. An attacker can force oversized request bodies through by supplying an application configuration value for limit that parses to null, such as an unparseable string or NaN. When an app relies on limit to cap body size, the parser skips enforcement and accepts arbitrarily large payloads, driving excessive memory and CPU usage and degrading or crashing the service.

Remediation

Upgrade body-parser to version 1.20.6, 2.3.0 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: cookie
  • Introduced through: cookie-parser@1.4.3

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › cookie-parser@1.4.3 › cookie@0.3.1
    Remediation: Upgrade to cookie-parser@1.4.7.

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 &lt; and > can be coded as &gt; 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

Cross-site Scripting (XSS) vulnerability report

medium severity
new

Inefficient Algorithmic Complexity

  • Vulnerable module: markdown-it
  • Introduced through: jsdoc@3.6.11

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › jsdoc@3.6.11 › markdown-it@12.3.2
    Remediation: Upgrade to jsdoc@4.0.3.

Overview

markdown-it is a modern pluggable markdown parser.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in the linkify rule (src/rules_core/linkify.ts) via input containing multiple fuzzy links. The arrayReplaceAt utility was called repeatedly inside the token-processing loop, causing each replacement to copy the entire token array, resulting in O(n²) time complexity as the number of links grows. An attacker can trigger excessive CPU consumption by supplying input with a large number of linkified URLs.

Remediation

Upgrade markdown-it to version 14.3.1, 15.0.1 or higher.

References

Inefficient Algorithmic Complexity vulnerability report

medium severity

Improper Handling of Unexpected Data Type

  • Vulnerable module: on-headers
  • Introduced through: morgan@1.9.0

Detailed paths

  • Introduced through: smooch-jwt@indira-active/smooch-jwt › morgan@1.9.0 › on-headers@1.0.2
    Remediation: Upgrade to morgan@1.10.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

Improper Handling of Unexpected Data Type vulnerability report