Skip to content

forever-2.0.0.tgz: 28 vulnerabilities (highest severity is: 9.8) [main] #27

@mdp-local

Description

@mdp-local
📂 Vulnerable Library - forever-2.0.0.tgz

A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever)

Path to dependency file: /package.json

Findings

Finding Severity 🎯 CVSS Exploit Maturity EPSS Library Type Fixed in Remediation Available Reachability
CVE-2021-44906 🟣 Critical 9.8 Not Defined < 1% minimist-1.2.5.tgz Transitive N/A
CVE-2021-44906 🟣 Critical 9.8 Not Defined < 1% minimist-1.2.0.tgz Transitive N/A
CVE-2021-44906 🟣 Critical 9.8 Not Defined < 1% minimist-0.0.8.tgz Transitive N/A
CVE-2021-44906 🟣 Critical 9.8 Not Defined < 1% minimist-0.0.10.tgz Transitive N/A
CVE-495493-603164 🟣 Critical 9.8 N/A N/A delegates-1.0.0.tgz Transitive N/A
CVE-814504-1548 🟣 Critical 9.8 N/A N/A isstream-0.1.2.tgz Transitive N/A
CVE-2021-32803 🔴 High 8.2 Not Defined < 1% tar-4.4.8.tgz Transitive N/A
CVE-2021-32804 🔴 High 8.2 Not Defined 85.5% tar-4.4.8.tgz Transitive N/A
CVE-2021-37701 🔴 High 8.2 Not Defined < 1% tar-4.4.8.tgz Transitive N/A
CVE-2021-37712 🔴 High 8.2 Not Defined < 1% tar-4.4.8.tgz Transitive N/A
CVE-2021-37713 🔴 High 8.2 Not Defined < 1% tar-4.4.8.tgz Transitive N/A
CVE-2019-20149 🔴 High 7.5 Not Defined < 1% kind-of-6.0.2.tgz Transitive N/A
CVE-2021-3820 🔴 High 7.5 Not Defined < 1% i-0.3.6.tgz Transitive N/A
CVE-2022-3517 🔴 High 7.5 Not Defined < 1% minimatch-3.0.4.tgz Transitive N/A
CVE-2022-38900 🔴 High 7.5 Not Defined < 1% decode-uri-component-0.2.0.tgz Transitive N/A
CVE-2024-4068 🔴 High 7.5 Not Defined < 1% braces-2.3.2.tgz Transitive N/A
WS-2018-0148 🔴 High 7.5 N/A N/A utile-0.2.1.tgz Transitive N/A
WS-2018-0148 🔴 High 7.5 N/A N/A utile-0.3.0.tgz Transitive N/A
CVE-2020-7774 🔴 High 7.3 Proof of concept < 1% y18n-3.2.1.tgz Transitive N/A
CVE-2020-7788 🔴 High 7.3 Proof of concept < 1% ini-1.3.5.tgz Transitive N/A
CVE-2022-21803 🔴 High 7.3 Proof of concept < 1% nconf-0.6.9.tgz Transitive N/A
CVE-2022-21803 🔴 High 7.3 Proof of concept < 1% nconf-0.10.0.tgz Transitive N/A
CVE-2020-7598 🟠 Medium 5.6 Not Defined < 1% minimist-1.2.0.tgz Transitive N/A
CVE-2020-7598 🟠 Medium 5.6 Not Defined < 1% minimist-0.0.8.tgz Transitive N/A
CVE-2020-7598 🟠 Medium 5.6 Not Defined < 1% minimist-0.0.10.tgz Transitive N/A
CVE-2020-7598 🟠 Medium 5.6 Not Defined < 1% minimist-1.2.5.tgz Transitive N/A
CVE-2020-28469 🟠 Medium 5.3 Not Defined < 1% glob-parent-3.1.0.tgz Transitive N/A
CVE-2025-5889 🟡 Low 3.1 Proof of concept < 1% brace-expansion-1.1.11.tgz Transitive N/A

Details

🟣CVE-2021-44906

Vulnerable Library - minimist-1.2.5.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • prettyjson-1.2.1.tgz
      • minimist-1.2.5.tgz (Vulnerable Library)

Vulnerability Details

Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

Publish Date: Mar 17, 2022 01:05 PM

URL: CVE-2021-44906

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 9.8


Suggested Fix

Type: Upgrade version

Origin: GHSA-xvch-5gv4-984h

Release Date: Mar 17, 2022 01:05 PM

Fix Resolution : minimist - 0.2.4,minimist - 1.2.6

🟣CVE-2021-44906

Vulnerable Library - minimist-1.2.0.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • rc-1.2.8.tgz
              • minimist-1.2.0.tgz (Vulnerable Library)

Vulnerability Details

Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

Publish Date: Mar 17, 2022 01:05 PM

URL: CVE-2021-44906

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 9.8


Suggested Fix

Type: Upgrade version

Origin: GHSA-xvch-5gv4-984h

Release Date: Mar 17, 2022 01:05 PM

Fix Resolution : minimist - 0.2.4,minimist - 1.2.6

🟣CVE-2021-44906

Vulnerable Library - minimist-0.0.8.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • mkdirp-0.5.1.tgz
              • minimist-0.0.8.tgz (Vulnerable Library)

Vulnerability Details

Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

Publish Date: Mar 17, 2022 01:05 PM

URL: CVE-2021-44906

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 9.8


Suggested Fix

Type: Upgrade version

Origin: GHSA-xvch-5gv4-984h

Release Date: Mar 17, 2022 01:05 PM

Fix Resolution : minimist - 0.2.4,minimist - 1.2.6

🟣CVE-2021-44906

Vulnerable Library - minimist-0.0.10.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • optimist-0.6.1.tgz
      • minimist-0.0.10.tgz (Vulnerable Library)

Vulnerability Details

Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

Publish Date: Mar 17, 2022 01:05 PM

URL: CVE-2021-44906

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 9.8


Suggested Fix

Type: Upgrade version

Origin: GHSA-xvch-5gv4-984h

Release Date: Mar 17, 2022 01:05 PM

Fix Resolution : minimist - 0.2.4,minimist - 1.2.6

🟣CVE-495493-603164

Vulnerable Library - delegates-1.0.0.tgz

delegate methods and accessors to another property

Library home page: https://registry.npmjs.org/delegates/-/delegates-1.0.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • npmlog-4.1.2.tgz
              • are-we-there-yet-1.1.5.tgz
                • delegates-1.0.0.tgz (Vulnerable Library)

Vulnerability Details

Created automatically by the test suite

Publish Date: Jun 07, 2010 05:12 PM

URL: CVE-495493-603164

Threat Assessment

Exploit Maturity:N/A

EPSS:N/A

Score: 9.8


Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🟣CVE-814504-1548

Vulnerable Library - isstream-0.1.2.tgz

Determine if an object is a Stream

Library home page: https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • winston-0.8.3.tgz
      • isstream-0.1.2.tgz (Vulnerable Library)

Vulnerability Details

Created automatically by the test suite

Publish Date: Jun 07, 2010 05:12 PM

URL: CVE-814504-1548

Threat Assessment

Exploit Maturity:N/A

EPSS:N/A

Score: 9.8


Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🔴CVE-2021-32803

Vulnerable Library - tar-4.4.8.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • tar-4.4.8.tgz (Vulnerable Library)

Vulnerability Details

The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. "node-tar" aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary "stat" calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the "node-tar" directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where "node-tar" checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass "node-tar" symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Aug 03, 2021 07:05 PM

URL: CVE-2021-32803

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 8.2


Suggested Fix

Type: Upgrade version

Origin: GHSA-r628-mhmh-qjhw

Release Date: Aug 03, 2021 07:05 PM

Fix Resolution : tar - 5.0.7,tar - 3.2.3,tar - 4.4.15,tar - 6.1.2

🔴CVE-2021-32804

Vulnerable Library - tar-4.4.8.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • tar-4.4.8.tgz (Vulnerable Library)

Vulnerability Details

The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the "preservePaths" flag is not set to "true". This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example "/home/user/.bashrc" would turn into "home/user/.bashrc". This logic was insufficient when file paths contained repeated path roots such as "////home/user/.bashrc". "node-tar" would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. "///home/user/.bashrc") would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom "onentry" method which sanitizes the "entry.path" or a "filter" method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Aug 03, 2021 07:10 PM

URL: CVE-2021-32804

Threat Assessment

Exploit Maturity:Not Defined

EPSS:85.5%

Score: 8.2


Suggested Fix

Type: Upgrade version

Origin: GHSA-3jfq-g458-7qm9

Release Date: Aug 03, 2021 07:10 PM

Fix Resolution : tar - 4.4.14,tar - 6.1.1,tar - 3.2.2,tar - 5.0.6

🔴CVE-2021-37701

Vulnerable Library - tar-4.4.8.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • tar-4.4.8.tgz (Vulnerable Library)

Vulnerability Details

The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both "" and "/" characters as path separators, however "" is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at "FOO", followed by a symbolic link named "foo", then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but not from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the "FOO" directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Aug 31, 2021 12:00 AM

URL: CVE-2021-37701

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 8.2


Suggested Fix

Type: Upgrade version

Origin: GHSA-9r2w-394v-53qc

Release Date: Aug 31, 2021 12:00 AM

Fix Resolution : tar - 5.0.8,tar - 4.4.16,tar - 6.1.7

🔴CVE-2021-37712

Vulnerable Library - tar-4.4.8.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • tar-4.4.8.tgz (Vulnerable Library)

Vulnerability Details

The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.

Publish Date: Aug 31, 2021 12:00 AM

URL: CVE-2021-37712

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 8.2


Suggested Fix

Type: Upgrade version

Origin: GHSA-qq89-hq3f-393p

Release Date: Aug 31, 2021 12:00 AM

Fix Resolution : tar - 5.0.10,tar - 4.4.18,tar - 6.1.9

🔴CVE-2021-37713

Vulnerable Library - tar-4.4.8.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • tar-4.4.8.tgz (Vulnerable Library)

Vulnerability Details

The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain ".." path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as "C:some\path". If the drive letter does not match the extraction target, for example "D:\extraction\dir", then the result of "path.resolve(extractionDirectory, entryPath)" would resolve against the current working directory on the "C:" drive, rather than the extraction target directory. Additionally, a ".." portion of the path could occur immediately after the drive letter, such as "C:../foo", and was not properly sanitized by the logic that checked for ".." within the normalized and split portions of the path. This only affects users of "node-tar" on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Aug 31, 2021 04:50 PM

URL: CVE-2021-37713

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 8.2


Suggested Fix

Type: Upgrade version

Origin: GHSA-5955-9wpr-37jh

Release Date: Aug 31, 2021 04:50 PM

Fix Resolution : tar - 6.1.9,tar - 5.0.10,tar - 4.4.18

🔴CVE-2019-20149

Vulnerable Library - kind-of-6.0.2.tgz

Get the native type of a value.

Library home page: https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • braces-2.3.2.tgz
          • snapdragon-0.8.2.tgz
            • base-0.11.2.tgz
              • define-property-1.0.0.tgz
                • is-descriptor-1.0.2.tgz
                  • kind-of-6.0.2.tgz (Vulnerable Library)

Vulnerability Details

ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.

Publish Date: Dec 30, 2019 06:25 PM

URL: CVE-2019-20149

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin: GHSA-6c8f-qphg-qjgp

Release Date: Dec 30, 2019 06:25 PM

Fix Resolution : kind-of - 6.0.3

🔴CVE-2021-3820

Vulnerable Library - i-0.3.6.tgz

custom inflections for nodejs

Library home page: https://registry.npmjs.org/i/-/i-0.3.6.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • utile-0.3.0.tgz
      • i-0.3.6.tgz (Vulnerable Library)

Vulnerability Details

inflect is vulnerable to Inefficient Regular Expression Complexity

Publish Date: Sep 27, 2021 12:25 PM

URL: CVE-2021-3820

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin: GHSA-x55w-vjjp-222r

Release Date: Sep 27, 2021 12:25 PM

Fix Resolution : i - 0.3.7,https://github.com/pksunkara/inflect.git - no_fix

🔴CVE-2022-3517

Vulnerable Library - minimatch-3.0.4.tgz

a glob matcher in javascript

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • rimraf-2.6.3.tgz
              • glob-7.1.3.tgz
                • minimatch-3.0.4.tgz (Vulnerable Library)

Vulnerability Details

A 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.

Publish Date: Oct 17, 2022 12:00 AM

URL: CVE-2022-3517

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin: GHSA-f8q6-p94x-37v3

Release Date: Oct 17, 2022 12:00 AM

Fix Resolution : minimatch - 3.0.5

🔴CVE-2022-38900

Vulnerable Library - decode-uri-component-0.2.0.tgz

A better decodeURIComponent

Library home page: https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • braces-2.3.2.tgz
          • snapdragon-0.8.2.tgz
            • source-map-resolve-0.5.2.tgz
              • decode-uri-component-0.2.0.tgz (Vulnerable Library)

Vulnerability Details

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.

Publish Date: Nov 28, 2022 12:00 AM

URL: CVE-2022-38900

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🔴CVE-2024-4068

Vulnerable Library - braces-2.3.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-2.3.2.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • braces-2.3.2.tgz (Vulnerable Library)

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. 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: May 13, 2024 10:06 AM

URL: CVE-2024-4068

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin: GHSA-grv7-fg5c-xmjg

Release Date: May 13, 2024 10:06 AM

Fix Resolution : braces - 3.0.3

🔴WS-2018-0148

Vulnerable Library - utile-0.2.1.tgz

A drop-in replacement for util with some additional advantageous functions

Library home page: https://registry.npmjs.org/utile/-/utile-0.2.1.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • flatiron-0.4.3.tgz
      • broadway-0.3.6.tgz
        • utile-0.2.1.tgz (Vulnerable Library)

Vulnerability Details

The utile npm module, version 0.3.0, allows to extract sensitive data from uninitialized memory or to cause a DoS by passing in a large number, in setups where typed user input can be passed (e.g. from JSON).

Publish Date: Jul 16, 2018 12:00 PM

URL: WS-2018-0148

Threat Assessment

Exploit Maturity:N/A

EPSS:N/A

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin: https://www.mend.io/vulnerability-database/WS-2018-0148

Release Date: Jan 16, 2018 07:35 AM

Fix Resolution : JetBrains.Rider.Frontend5 - 213.0.20211008.154703-eap03

🔴WS-2018-0148

Vulnerable Library - utile-0.3.0.tgz

A drop-in replacement for util with some additional advantageous functions

Library home page: https://registry.npmjs.org/utile/-/utile-0.3.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • utile-0.3.0.tgz (Vulnerable Library)

Vulnerability Details

The utile npm module, version 0.3.0, allows to extract sensitive data from uninitialized memory or to cause a DoS by passing in a large number, in setups where typed user input can be passed (e.g. from JSON).

Publish Date: Jul 16, 2018 12:00 PM

URL: WS-2018-0148

Threat Assessment

Exploit Maturity:N/A

EPSS:N/A

Score: 7.5


Suggested Fix

Type: Upgrade version

Origin: https://www.mend.io/vulnerability-database/WS-2018-0148

Release Date: Jan 16, 2018 07:35 AM

Fix Resolution : JetBrains.Rider.Frontend5 - 213.0.20211008.154703-eap03

🔴CVE-2020-7774

Vulnerable Library - y18n-3.2.1.tgz

the bare-bones internationalization library used by yargs

Library home page: https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • nconf-0.10.0.tgz
      • yargs-3.32.0.tgz
        • y18n-3.2.1.tgz (Vulnerable Library)

Vulnerability Details

The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.

Publish Date: Nov 17, 2020 12:30 PM

URL: CVE-2020-7774

Threat Assessment

Exploit Maturity:Proof of concept

EPSS:< 1%

Score: 7.3


Suggested Fix

Type: Upgrade version

Origin: GHSA-c4w7-xm78-47vh

Release Date: Nov 17, 2020 12:30 PM

Fix Resolution : y18n - 3.2.2,y18n - 4.0.1,y18n - 5.0.5

🔴CVE-2020-7788

Vulnerable Library - ini-1.3.5.tgz

An ini encoder/decoder for node

Library home page: https://registry.npmjs.org/ini/-/ini-1.3.5.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • rc-1.2.8.tgz
              • ini-1.3.5.tgz (Vulnerable Library)

Vulnerability Details

This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.

Publish Date: Dec 11, 2020 10:45 AM

URL: CVE-2020-7788

Threat Assessment

Exploit Maturity:Proof of concept

EPSS:< 1%

Score: 7.3


Suggested Fix

Type: Upgrade version

Origin: GHSA-qqgx-2p2h-9c37

Release Date: Dec 11, 2020 10:45 AM

Fix Resolution : ini - 1.3.6

🔴CVE-2022-21803

Vulnerable Library - nconf-0.6.9.tgz

Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.

Library home page: https://registry.npmjs.org/nconf/-/nconf-0.6.9.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • flatiron-0.4.3.tgz
      • broadway-0.3.6.tgz
        • nconf-0.6.9.tgz (Vulnerable Library)

Vulnerability Details

This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype.

Publish Date: Apr 12, 2022 03:20 PM

URL: CVE-2022-21803

Threat Assessment

Exploit Maturity:Proof of concept

EPSS:< 1%

Score: 7.3


Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🔴CVE-2022-21803

Vulnerable Library - nconf-0.10.0.tgz

Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.

Library home page: https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • nconf-0.10.0.tgz (Vulnerable Library)

Vulnerability Details

This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype.

Publish Date: Apr 12, 2022 03:20 PM

URL: CVE-2022-21803

Threat Assessment

Exploit Maturity:Proof of concept

EPSS:< 1%

Score: 7.3


Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🟠CVE-2020-7598

Vulnerable Library - minimist-1.2.0.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • rc-1.2.8.tgz
              • minimist-1.2.0.tgz (Vulnerable Library)

Vulnerability Details

minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Mar 11, 2020 09:40 PM

URL: CVE-2020-7598

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 5.6


Suggested Fix

Type: Upgrade version

Origin: GHSA-vh95-rmgr-6w4m

Release Date: Mar 11, 2020 09:40 PM

Fix Resolution : minimist - 1.2.3,minimist - 0.2.1

🟠CVE-2020-7598

Vulnerable Library - minimist-0.0.8.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • mkdirp-0.5.1.tgz
              • minimist-0.0.8.tgz (Vulnerable Library)

Vulnerability Details

minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Mar 11, 2020 09:40 PM

URL: CVE-2020-7598

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 5.6


Suggested Fix

Type: Upgrade version

Origin: GHSA-vh95-rmgr-6w4m

Release Date: Mar 11, 2020 09:40 PM

Fix Resolution : minimist - 1.2.3,minimist - 0.2.1

🟠CVE-2020-7598

Vulnerable Library - minimist-0.0.10.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • optimist-0.6.1.tgz
      • minimist-0.0.10.tgz (Vulnerable Library)

Vulnerability Details

minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Mar 11, 2020 09:40 PM

URL: CVE-2020-7598

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 5.6


Suggested Fix

Type: Upgrade version

Origin: GHSA-vh95-rmgr-6w4m

Release Date: Mar 11, 2020 09:40 PM

Fix Resolution : minimist - 1.2.3,minimist - 0.2.1

🟠CVE-2020-7598

Vulnerable Library - minimist-1.2.5.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • prettyjson-1.2.1.tgz
      • minimist-1.2.5.tgz (Vulnerable Library)

Vulnerability Details

minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Mar 11, 2020 09:40 PM

URL: CVE-2020-7598

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 5.6


Suggested Fix

Type: Upgrade version

Origin: GHSA-vh95-rmgr-6w4m

Release Date: Mar 11, 2020 09:40 PM

Fix Resolution : minimist - 1.2.3,minimist - 0.2.1

🟠CVE-2020-28469

Vulnerable Library - glob-parent-3.1.0.tgz

Strips glob magic from a string to provide the parent directory path

Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • glob-parent-3.1.0.tgz (Vulnerable Library)

Vulnerability Details

This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.

Publish Date: Jun 03, 2021 03:15 PM

URL: CVE-2020-28469

Threat Assessment

Exploit Maturity:Not Defined

EPSS:< 1%

Score: 5.3


Suggested Fix

Type: Upgrade version

Origin: GHSA-ww39-953v-wcq6

Release Date: Jun 03, 2021 03:15 PM

Fix Resolution : glob-parent - 5.1.2

🟡CVE-2025-5889

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Path to dependency file: /package.json

Dependency Hierarchy:

  • forever-2.0.0.tgz (Root Library)
    • forever-monitor-2.0.0.tgz
      • chokidar-2.1.8.tgz
        • fsevents-1.2.9.tgz
          • node-pre-gyp-0.12.0.tgz
            • rimraf-2.6.3.tgz
              • glob-7.1.3.tgz
                • minimatch-3.0.4.tgz
                  • brace-expansion-1.1.11.tgz (Vulnerable Library)

Vulnerability Details

A vulnerability was found in juliangruber brace-expansion up to 1.1.11. It has been rated as problematic. Affected by this issue is the function expand of the file index.js. The manipulation leads to inefficient regular expression complexity. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is a5b98a4f30d7813266b221435e1eaaf25a1b0ac5. It is recommended to apply a patch to fix this issue.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: Jun 09, 2025 06:16 PM

URL: CVE-2025-5889

Threat Assessment

Exploit Maturity:Proof of concept

EPSS:< 1%

Score: 3.1


Suggested Fix

Type: Upgrade version

Origin: GHSA-v6h2-p8h4-qcjw

Release Date: Jun 09, 2025 06:16 PM

Fix Resolution : brace-expansion - 4.0.1,https://github.com/juliangruber/brace-expansion.git - no_fix,brace-expansion - 3.0.1,brace-expansion - 2.0.2,brace-expansion - 1.1.12

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions