contact-center-main-app-1.0.0.tgz: 9 vulnerabilities (highest severity is: 7.5)

[mend-for-github-com]

Vulnerable Library - contact-center-main-app-1.0.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/jose/package.json

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (contact-center-main-app version)	Remediation Possible**
CVE-2024-51479	High	7.5	next-13.5.4.tgz	Transitive	N/A*	❌
CVE-2024-46982	High	7.5	next-13.5.4.tgz	Transitive	N/A*	❌
CVE-2024-4068	High	7.5	braces-3.0.2.tgz	Transitive	N/A*	❌
CVE-2024-34351	High	7.5	next-13.5.4.tgz	Transitive	N/A*	❌
CVE-2024-47831	Medium	5.9	next-13.5.4.tgz	Transitive	N/A*	❌
CVE-2024-56332	Medium	5.3	next-13.5.4.tgz	Transitive	N/A*	❌
CVE-2024-4067	Medium	5.3	micromatch-4.0.5.tgz	Transitive	N/A*	❌
CVE-2024-28176	Medium	4.9	jose-4.15.3.tgz	Transitive	N/A*	❌
CVE-2024-27088	Low	0.0	es5-ext-0.10.62.tgz	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-51479

Vulnerable Library - next-13.5.4.tgz

Library home page: https://registry.npmjs.org/next/-/next-13.5.4.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/next/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • ❌ next-13.5.4.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] "https://example.com/" * [Affected] "https://example.com/foo" * [Not affected] "https://example.com/foo/bar". This issue is patched in Next.js "14.2.15" and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability.

Publish Date: 2024-12-17

URL: CVE-2024-51479

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-7gfc-8cq8-jh5f

Release Date: 2024-12-17

Fix Resolution: next - 14.2.15

CVE-2024-46982

Vulnerable Library - next-13.5.4.tgz

Library home page: https://registry.npmjs.org/next/-/next-13.5.4.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/next/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • ❌ next-13.5.4.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, stale-while-revalidate header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. pages/dashboard.tsx not pages/blog/[slug].tsx. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Publish Date: 2024-09-17

URL: CVE-2024-46982

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-gp8f-8m3g-qvj9

Release Date: 2024-09-17

Fix Resolution: next - 13.5.7,14.2.10

CVE-2024-4068

Vulnerable Library - braces-3.0.2.tgz

Bash-like brace expansion, implemented in JavaScript. Safer than other brace expansion libs, with complete support for the Bash 4.3 braces specification, without sacrificing speed.

Library home page: https://registry.npmjs.org/braces/-/braces-3.0.2.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/braces/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • tailwindcss-3.3.3.tgz
    • chokidar-3.5.3.tgz
      • ❌ braces-3.0.2.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

The NPM package braces, versions prior to 3.0.3, fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
Mend Note: After conducting a further research, it was concluded that CVE-2024-4068 does not contain a high security risk that reflects the NVD score, but should be kept for users' awareness. Users of braces should follow the fix recommendation as noted.

Publish Date: 2024-05-13

URL: CVE-2024-4068

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2024-05-13

Fix Resolution: braces - 3.0.3

CVE-2024-34351

Vulnerable Library - next-13.5.4.tgz

Library home page: https://registry.npmjs.org/next/-/next-13.5.4.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/next/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • ❌ next-13.5.4.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the Host header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a /. This vulnerability was fixed in Next.js 14.1.1.

Publish Date: 2024-05-09

URL: CVE-2024-34351

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-77r5-gw3j-2mpf

Release Date: 2024-05-09

Fix Resolution: next - 14.1.1

CVE-2024-47831

Vulnerable Library - next-13.5.4.tgz

Library home page: https://registry.npmjs.org/next/-/next-13.5.4.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/next/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • ❌ next-13.5.4.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

Next.js is a React Framework for the Web. Cersions on the 10.x, 11.x, 12.x, 13.x, and 14.x branches before version 14.2.7 contain a vulnerability in the image optimization feature which allows for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption. Neither the next.config.js file that is configured with images.unoptimized set to true or images.loader set to a non-default value nor the Next.js application that is hosted on Vercel are affected. This issue was fully patched in Next.js 14.2.7. As a workaround, ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.

Publish Date: 2024-10-14

URL: CVE-2024-47831

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-g77x-44xx-532m

Release Date: 2024-10-14

Fix Resolution: next - 14.2.7

CVE-2024-56332

Vulnerable Library - next-13.5.4.tgz

Library home page: https://registry.npmjs.org/next/-/next-13.5.4.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/next/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • ❌ next-13.5.4.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

Next.js is a React framework for building full-stack web applications. Starting in version 13.0.0 and prior to versions 13.5.8, 14.2.21, and 15.1.2, Next.js is vulnerable to a Denial of Service (DoS) attack that allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. This vulnerability can also be used as a Denial of Wallet (DoW) attack when deployed in providers billing by response times. (Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.). Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid "Content-Length" header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. The issue was resolved in Next.js 13.5.8, 14.2.21, and 15.1.2. We recommend that users upgrade to a safe version. There are no official workarounds.

Publish Date: 2025-01-03

URL: CVE-2024-56332

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-7m27-7ghc-44w9

Release Date: 2025-01-03

Fix Resolution: next - 13.5.8,14.2.21,15.1.2

CVE-2024-4067

Vulnerable Library - micromatch-4.0.5.tgz

Glob matching for javascript/node.js. A replacement and faster alternative to minimatch and multimatch.

Library home page: https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/micromatch/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • tailwindcss-3.3.3.tgz
    • ❌ micromatch-4.0.5.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

The NPM package micromatch prior to 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persists. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching. This issue was fixed in version 4.0.8.
Mend Note: After conducting a further research, it was concluded that CVE-2024-4067 should not reflect the security risk score in NVD, but will be kept for users' awareness.

Publish Date: 2024-05-13

URL: CVE-2024-4067

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2024-05-13

Fix Resolution: micromatch - 4.0.8

CVE-2024-28176

Vulnerable Library - jose-4.15.3.tgz

Library home page: https://registry.npmjs.org/jose/-/jose-4.15.3.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/jose/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • auth-helpers-nextjs-0.6.1.tgz
    • auth-helpers-shared-0.3.4.tgz
      • ❌ jose-4.15.3.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

jose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has
been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.

Publish Date: 2024-03-09

URL: CVE-2024-28176

CVSS 3 Score Details (4.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: High
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-hhhv-q57g-882q

Release Date: 2024-03-09

Fix Resolution: jose - 2.0.7,4.15.5, jose-node-cjs-runtime - 4.15.5, jose-node-esm-runtime - 4.15.5

CVE-2024-27088

Vulnerable Library - es5-ext-0.10.62.tgz

ECMAScript extensions and shims

Library home page: https://registry.npmjs.org/es5-ext/-/es5-ext-0.10.62.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/es5-ext/package.json

Dependency Hierarchy:

• contact-center-main-app-1.0.0.tgz (Root Library)
  • supabase-js-2.38.0.tgz
    • realtime-js-2.8.0.tgz
      • websocket-1.0.34.tgz
        • ❌ es5-ext-0.10.62.tgz (Vulnerable Library)

Found in HEAD commit: 1f437ab967b4e4099ef9e4770a4ad9e1cd01b1f4

Found in base branch: main

Vulnerability Details

es5-ext contains ECMAScript 5 extensions. Passing functions with very long names or complex default argument names into function#copy or function#toStringTokens may cause the script to stall. The vulnerability is patched in v0.10.63.

Publish Date: 2024-02-26

URL: CVE-2024-27088

CVSS 3 Score Details (0.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: Low
  • Privileges Required: High
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2024-27088

Release Date: 2024-02-26

Fix Resolution: es5-ext - 0.10.63

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.