shaneclarke-whitesource / multi-juicer Goto Github PK
View Code? Open in Web Editor NEWThis project forked from realself/multi-juicer
Run Capture the Flags and Security Trainings with OWASP Juice Shop
License: Apache License 2.0
This project forked from realself/multi-juicer
Run Capture the Flags and Security Trainings with OWASP Juice Shop
License: Apache License 2.0
Small footprint URL parser that works seamlessly across Node.js and browser environments
Library home page: https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/url-parse/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.8.
Publish Date: 2022-02-20
URL: CVE-2022-0686
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0686
Release Date: 2022-02-20
Fix Resolution (url-parse): 1.5.8
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/node-forge/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
forge is vulnerable to URL Redirection to Untrusted Site
Publish Date: 2022-01-06
URL: CVE-2022-0122
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-gf8q-jrpm-jvxq
Release Date: 2022-01-06
Fix Resolution (node-forge): 1.0.0
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Embedded JavaScript templates
Library home page: https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/ejs/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Arbitrary Code Injection vulnerability was found in ejs before 3.1.6. Caused by filename which isn't sanitized for display.
Publish Date: 2021-01-22
URL: WS-2021-0153
Base Score Metrics:
Type: Upgrade version
Release Date: 2021-01-22
Fix Resolution (ejs): 3.1.6
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/node-forge/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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.
Publish Date: 2022-01-08
URL: WS-2022-0008
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-5rrq-pxf6-6jx5
Release Date: 2022-01-08
Fix Resolution (node-forge): 1.0.0
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
Library home page: https://registry.npmjs.org/browserslist/-/browserslist-4.14.2.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/react-dev-utils/node_modules/browserslist/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The package browserslist from 4.0.0 and before 4.16.5 are vulnerable to Regular Expression Denial of Service (ReDoS) during parsing of queries.
Publish Date: 2021-04-28
URL: CVE-2021-23364
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23364
Release Date: 2021-04-28
Fix Resolution (browserslist): 4.16.5
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/tar/package.json,/juice-balancer/node_modules/tar/package.json,/juice-balancer/ui/node_modules/tar/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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: 2021-08-31
URL: CVE-2021-37712
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: 2021-08-31
Fix Resolution (tar): 6.1.9
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
A tiny (108 bytes), secure URL-friendly unique string ID generator
Library home page: https://registry.npmjs.org/nanoid/-/nanoid-3.1.22.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/postcss-safe-parser/node_modules/nanoid/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The package nanoid from 3.0.0 and before 3.1.31 are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.
Publish Date: 2022-01-14
URL: CVE-2021-23566
Base Score Metrics:
Type: Upgrade version
Release Date: 2022-01-14
Fix Resolution (nanoid): 3.1.31
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Tool for transforming styles with JS plugins
Library home page: https://registry.npmjs.org/postcss/-/postcss-8.2.10.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/postcss-safe-parser/node_modules/postcss/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern /*\s* sourceMappingURL=(.*).
Publish Date: 2021-04-26
URL: CVE-2021-23382
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382
Release Date: 2021-04-26
Fix Resolution (postcss): 8.2.13
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Library home page: https://registry.npmjs.org/terser/-/terser-5.6.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/terser-webpack-plugin/node_modules/terser/package.json
Dependency Hierarchy:
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Library home page: https://registry.npmjs.org/terser/-/terser-4.8.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/terser/package.json
Dependency Hierarchy:
Found in base branch: master
The package terser before 4.8.1, from 5.0.0 and before 5.14.2 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.
Publish Date: 2022-07-15
URL: CVE-2022-25858
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25858
Release Date: 2022-07-15
Fix Resolution (terser): 5.14.2
Direct dependency fix Resolution (react-scripts): 5.0.0
Fix Resolution (terser): 4.8.1
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Portable Unix shell commands for Node.js
Library home page: https://registry.npmjs.org/shelljs/-/shelljs-0.8.4.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/shelljs/package.json,/juice-balancer/node_modules/shelljs/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
shelljs is vulnerable to Improper Privilege Management
Publish Date: 2022-01-11
URL: CVE-2022-0144
Base Score Metrics:
Type: Upgrade version
Release Date: 2022-01-11
Fix Resolution (shelljs): 0.8.5
Direct dependency fix Resolution (@kubernetes/client-node): 0.16.2
⛑️ Automatic Remediation is available for this issue
parse argument options
Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/minimist/package.json,/juice-balancer/ui/node_modules/minimist/package.json,/cleaner/node_modules/minimist/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
Publish Date: 2022-03-17
URL: CVE-2021-44906
Base Score Metrics:
Type: Upgrade version
Release Date: 2022-03-17
Fix Resolution (minimist): 1.2.6
Direct dependency fix Resolution (react-scripts): 5.0.1
⛑️ Automatic Remediation is available for this issue
Extract the non-magic parent path from a glob string.
Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/glob-parent/package.json,/juice-balancer/ui/node_modules/glob-parent/package.json,/juice-balancer/node_modules/glob-parent/package.json
Dependency Hierarchy:
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: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/webpack-dev-server/node_modules/glob-parent/package.json,/juice-balancer/ui/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json
Dependency Hierarchy:
Found in base branch: master
The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS)
Publish Date: 2021-06-22
URL: CVE-2021-35065
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-cj88-88mr-972w
Release Date: 2021-06-22
Fix Resolution (glob-parent): 6.0.1
Direct dependency fix Resolution (eslint): 8.0.0
Fix Resolution (glob-parent): 6.0.1
Direct dependency fix Resolution (react-scripts): 5.0.1
⛑️ Automatic Remediation is available for this issue
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.21.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/axios/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository axios/axios prior to 0.26.
Publish Date: 2022-05-03
URL: CVE-2022-1214
Base Score Metrics:
Type: Upgrade version
Origin: https://huntr.dev/bounties/ef7b4ab6-a3f6-4268-a21a-e7104d344607/
Release Date: 2022-05-03
Fix Resolution: 0.26.0
⛑️ Automatic Remediation is available for this issue
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/tar/package.json,/juice-balancer/node_modules/tar/package.json,/juice-balancer/ui/node_modules/tar/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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.
Publish Date: 2021-08-31
URL: CVE-2021-37713
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: 2021-08-31
Fix Resolution (tar): 6.1.9
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/node-forge/package.json
Dependency Hierarchy:
Found in base branch: master
In node-forge before 1.0.0 he 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.
Publish Date: 2022-01-08
URL: WS-2022-0007
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-gf8q-jrpm-jvxq
Release Date: 2022-01-08
Fix Resolution: node-forge - 1.0.0
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/node-forge/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Forge (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.
Publish Date: 2022-03-18
URL: CVE-2022-24773
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24773
Release Date: 2022-03-18
Fix Resolution (node-forge): 1.3.0
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/node-forge/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Forge (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.
Publish Date: 2022-03-18
URL: CVE-2022-24772
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24772
Release Date: 2022-03-18
Fix Resolution (node-forge): 1.3.0
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/node-forge/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Forge (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.
Publish Date: 2022-03-18
URL: CVE-2022-24771
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771
Release Date: 2022-03-18
Fix Resolution (node-forge): 1.3.0
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Human-friendly and powerful HTTP request library for Node.js
Library home page: https://registry.npmjs.org/got/-/got-11.8.2.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/got/package.json,/cleaner/node_modules/got/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The got package before 12.1.0 (also fixed in 11.8.5) for Node.js allows a redirect to a UNIX socket.
Publish Date: 2022-06-18
URL: CVE-2022-33987
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33987
Release Date: 2022-06-18
Fix Resolution (got): 11.8.6
Direct dependency fix Resolution (@kubernetes/client-node): 0.17.1
⛑️ Automatic Remediation is available for this issue
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: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/webpack-dev-server/node_modules/glob-parent/package.json,/juice-balancer/ui/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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: 2021-06-03
URL: CVE-2020-28469
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469
Release Date: 2021-06-03
Fix Resolution (glob-parent): 5.1.2
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Small footprint URL parser that works seamlessly across Node.js and browser environments
Library home page: https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/url-parse/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.7.
Publish Date: 2022-02-17
URL: CVE-2022-0639
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0639
Release Date: 2022-02-17
Fix Resolution (url-parse): 1.5.7
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/tar/package.json,/juice-balancer/node_modules/tar/package.json,/juice-balancer/ui/node_modules/tar/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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.
Publish Date: 2021-08-03
URL: CVE-2021-32803
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-r628-mhmh-qjhw
Release Date: 2021-08-03
Fix Resolution (tar): 6.1.2
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Create your next immutable state by mutating the current one
Library home page: https://registry.npmjs.org/immer/-/immer-8.0.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/immer/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
This affects the package immer before 9.0.6. A type confusion vulnerability can lead to a bypass of CVE-2020-28477 when the user-provided keys used in the path parameter are arrays. In particular, this bypass is possible because the condition (p === "proto" || p === "constructor") in applyPatches_ returns false if p is ['proto'] (or ['constructor']). The === operator (strict equality operator) returns false if the operands have different type.
Publish Date: 2021-09-01
URL: CVE-2021-23436
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23436
Release Date: 2021-09-01
Fix Resolution (immer): 9.0.6
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.21.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/axios/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
axios is vulnerable to Inefficient Regular Expression Complexity
Publish Date: 2021-08-31
URL: CVE-2021-3749
Base Score Metrics:
Type: Upgrade version
Origin: https://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31/
Release Date: 2021-08-31
Fix Resolution: 0.21.2
⛑️ Automatic Remediation is available for this issue
performant nth-check parser & compiler
Library home page: https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/nth-check/package.json
Dependency Hierarchy:
Parses and compiles CSS nth-checks to highly optimized functions.
Library home page: https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/renderkid/node_modules/nth-check/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
nth-check is vulnerable to Inefficient Regular Expression Complexity
Publish Date: 2021-09-17
URL: CVE-2021-3803
Base Score Metrics:
Type: Upgrade version
Release Date: 2021-09-17
Fix Resolution (nth-check): 2.0.1
Direct dependency fix Resolution (react-scripts): 5.0.1
Fix Resolution (nth-check): 2.0.1
Direct dependency fix Resolution (react-scripts): 5.0.1
⛑️ Automatic Remediation is available for this issue
Normalize a URL
Library home page: https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/normalize-url/package.json
Dependency Hierarchy:
Normalize a URL
Library home page: https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/postcss-normalize-url/node_modules/normalize-url/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
Publish Date: 2021-05-24
URL: CVE-2021-33502
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502
Release Date: 2021-05-24
Fix Resolution (normalize-url): 4.5.1
Direct dependency fix Resolution (react-scripts): 5.0.0
Fix Resolution (normalize-url): 4.5.1
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
[mirror] Go text processing support
Library home page: https://proxy.golang.org/github.com/golang/text/@v/v0.3.4.zip
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
In x/text in Go 1.15.4, an "index out of range" panic occurs in language.ParseAcceptLanguage while parsing the -u- extension. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.)
Publish Date: 2021-01-02
URL: CVE-2020-28851
Base Score Metrics:
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2020-28851
Release Date: 2021-01-02
Fix Resolution: golang-golang-x-text-dev - 0.3.6-1,0.3.6-1
JavaScript micro templates.
Library home page: https://registry.npmjs.org/tmpl/-/tmpl-1.0.4.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/tmpl/package.json,/juice-balancer/node_modules/tmpl/package.json,/juice-balancer/ui/node_modules/tmpl/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
nodejs-tmpl is vulnerable to Inefficient Regular Expression Complexity
Publish Date: 2021-09-15
URL: CVE-2021-3777
Base Score Metrics:
Type: Upgrade version
Release Date: 2021-09-15
Fix Resolution (tmpl): 1.0.5
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
a CSS selector parser
Library home page: https://registry.npmjs.org/css-what/-/css-what-3.4.2.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/css-what/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.
Publish Date: 2021-05-28
URL: CVE-2021-33587
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587
Release Date: 2021-05-28
Fix Resolution (css-what): 5.0.1
Direct dependency fix Resolution (react-scripts): 5.0.1
⛑️ Automatic Remediation is available for this issue
[mirror] Go text processing support
Library home page: https://proxy.golang.org/github.com/golang/text/@v/v0.3.4.zip
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
In x/text in Go before v0.3.5, a "slice bounds out of range" panic occurs in language.ParseAcceptLanguage while processing a BCP 47 tag. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.)
Publish Date: 2021-01-02
URL: CVE-2020-28852
Base Score Metrics:
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2020-28852
Release Date: 2021-01-02
Fix Resolution: golang-golang-x-text-dev - 0.3.5-1,0.3.5-1
quote and parse shell commands
Library home page: https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/shell-quote/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z] instead of the correct {A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
Publish Date: 2021-10-21
URL: CVE-2021-42740
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740
Release Date: 2021-10-21
Fix Resolution (shell-quote): 1.7.3
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Small footprint URL parser that works seamlessly across Node.js and browser environments
Library home page: https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/url-parse/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.
Publish Date: 2022-02-14
URL: CVE-2022-0512
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512
Release Date: 2022-02-14
Fix Resolution (url-parse): 1.5.6
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
get colors in your node.js console
Library home page: https://registry.npmjs.org/colors/-/colors-1.4.0.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/colors/package.json
Dependency Hierarchy:
Found in base branch: master
The package colors after 1.4.0 are vulnerable to Denial of Service (DoS) that was introduced through an infinite loop in the americanFlag module. Unfortunately this appears to have been a purposeful attempt by a maintainer of colors to make the package unusable, other maintainers' controls over this package appear to have been revoked in an attempt to prevent them from fixing the issue. Vulnerable Code js for (let i = 666; i < Infinity; i++;) { Alternative Remediation Suggested * Pin dependancy to 1.4.0
Publish Date: 2022-01-14
URL: CVE-2021-23567
Base Score Metrics:
Regular expression for matching ANSI escape codes
Library home page: https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/ansi-regex/package.json,/juice-balancer/node_modules/ansi-regex/package.json,/cleaner/node_modules/ansi-regex/package.json
Dependency Hierarchy:
Regular expression for matching ANSI escape codes
Library home page: https://registry.npmjs.org/ansi-regex/-/ansi-regex-4.1.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/webpack-dev-server/node_modules/cliui/node_modules/ansi-regex/package.json,/juice-balancer/ui/node_modules/webpack-dev-server/node_modules/string-width/node_modules/ansi-regex/package.json,/juice-balancer/ui/node_modules/webpack-dev-server/node_modules/wrap-ansi/node_modules/ansi-regex/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
ansi-regex is vulnerable to Inefficient Regular Expression Complexity
Publish Date: 2021-09-17
URL: CVE-2021-3807
Base Score Metrics:
Type: Upgrade version
Origin: https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/
Release Date: 2021-09-17
Fix Resolution (ansi-regex): 5.0.1
Direct dependency fix Resolution (react-scripts): 5.0.0
Fix Resolution (ansi-regex): 4.1.1
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Higher-order functions and common patterns for asynchronous code
Library home page: https://registry.npmjs.org/async/-/async-2.6.3.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/async/package.json
Dependency Hierarchy:
Higher-order functions and common patterns for asynchronous code
Library home page: https://registry.npmjs.org/async/-/async-3.2.0.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/async/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues() method, aka lib/internal/iterator.js createObjectIterator prototype pollution.
Publish Date: 2022-04-06
URL: CVE-2021-43138
Base Score Metrics:
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2021-43138
Release Date: 2022-04-06
Fix Resolution (async): 2.6.4
Direct dependency fix Resolution (react-scripts): 5.0.0
Fix Resolution (async): 3.2.2
Direct dependency fix Resolution (winston): 3.4.0
⛑️ Automatic Remediation is available for this issue
HTTP and HTTPS modules that follow redirects.
Library home page: https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.13.0.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/follow-redirects/package.json,/juice-balancer/ui/node_modules/follow-redirects/package.json
Dependency Hierarchy:
Found in base branch: master
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor
Publish Date: 2022-01-10
URL: CVE-2022-0155
Base Score Metrics:
Type: Upgrade version
Origin: https://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/
Release Date: 2022-01-10
Fix Resolution: follow-redirects - v1.14.7
Embedded JavaScript templates
Library home page: https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/ejs/package.json
Dependency Hierarchy:
Embedded JavaScript templates
Library home page: https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/source-map-explorer/node_modules/ejs/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
Publish Date: 2022-04-25
URL: CVE-2022-29078
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~
Release Date: 2022-04-25
Fix Resolution (ejs): 3.1.7
Direct dependency fix Resolution (react-scripts): 5.0.1
⛑️ Automatic Remediation is available for this issue
An elegant lib that converts the chalked (ANSI) text to HTML.
Library home page: https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/ansi-html/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
This 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.
Publish Date: 2021-08-18
URL: CVE-2021-23424
Base Score Metrics:
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2021-23424
Release Date: 2021-08-18
Fix Resolution (ansi-html): 0.0.8
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
JSON Schema validation and specifications
Library home page: https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/json-schema/package.json,/juice-balancer/ui/node_modules/json-schema/package.json,/juice-balancer/node_modules/json-schema/package.json
Dependency Hierarchy:
Found in base branch: master
json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Publish Date: 2021-11-13
URL: CVE-2021-3918
Base Score Metrics:
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2021-3918
Release Date: 2021-11-13
Fix Resolution (json-schema): 0.4.0
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Small footprint URL parser that works seamlessly across Node.js and browser environments
Library home page: https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/url-parse/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
url-parse is vulnerable to URL Redirection to Untrusted Site
Publish Date: 2021-07-26
URL: CVE-2021-3664
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3664
Release Date: 2021-07-26
Fix Resolution (url-parse): 1.5.2
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/tar/package.json,/juice-balancer/node_modules/tar/package.json,/juice-balancer/ui/node_modules/tar/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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.
Publish Date: 2021-08-03
URL: CVE-2021-32804
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-3jfq-g458-7qm9
Release Date: 2021-08-03
Fix Resolution (tar): 6.1.1
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Node.js path.parse() ponyfill
Library home page: https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/path-parse/package.json,/cleaner/node_modules/path-parse/package.json,/juice-balancer/node_modules/path-parse/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
Publish Date: 2021-05-04
URL: CVE-2021-23343
Base Score Metrics:
Type: Upgrade version
Release Date: 2021-05-04
Fix Resolution (path-parse): 1.0.7
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
W3C compliant EventSource client for Node.js and browser (polyfill)
Library home page: https://registry.npmjs.org/eventsource/-/eventsource-1.1.0.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/eventsource/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository eventsource/eventsource prior to v2.0.2.
Publish Date: 2022-05-12
URL: CVE-2022-1650
Base Score Metrics:
Type: Upgrade version
Release Date: 2022-05-12
Fix Resolution (eventsource): 1.1.1
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
Create your next immutable state by mutating the current one
Library home page: https://registry.npmjs.org/immer/-/immer-8.0.1.tgz
Path to dependency file: /juice-balancer/ui/package.json
Path to vulnerable library: /juice-balancer/ui/node_modules/immer/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
immer is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Publish Date: 2021-09-02
URL: CVE-2021-3757
Base Score Metrics:
Type: Upgrade version
Origin: https://huntr.dev/bounties/23d38099-71cd-42ed-a77a-71e68094adfa/
Release Date: 2021-09-02
Fix Resolution (immer): 9.0.6
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
[mirror] Go supplementary network libraries
Library home page: https://proxy.golang.org/github.com/golang/net/@v/v0.0.0-20210224082022-3d97a244fca7.zip
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
net/http in Go before 1.15.12 and 1.16.x before 1.16.4 allows remote attackers to cause a denial of service (panic) via a large header to ReadRequest or ReadResponse. Server, Transport, and Client can each be affected in some configurations.
Publish Date: 2021-05-27
URL: CVE-2021-31525
Base Score Metrics:
Type: Upgrade version
Origin: https://bugzilla.redhat.com/show_bug.cgi?id=1958341
Release Date: 2021-05-27
Fix Resolution: golang - v1.15.12,v1.16.4,v1.17.0
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz
Path to dependency file: /cleaner/package.json
Path to vulnerable library: /cleaner/node_modules/tar/package.json,/juice-balancer/node_modules/tar/package.json,/juice-balancer/ui/node_modules/tar/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
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.
Publish Date: 2021-08-31
URL: CVE-2021-37701
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: 2021-08-31
Fix Resolution (tar): 6.1.7
Direct dependency fix Resolution (react-scripts): 5.0.0
⛑️ Automatic Remediation is available for this issue
[mirror] Go supplementary network libraries
Library home page: https://proxy.golang.org/github.com/golang/net/@v/v0.0.0-20210224082022-3d97a244fca7.zip
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
golang.org/x/net before v0.0.0-20210520170846-37e1c6afe023 allows attackers to cause a denial of service (infinite loop) via crafted ParseFragment input.
Publish Date: 2021-05-26
URL: CVE-2021-33194
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194
Release Date: 2021-05-26
Fix Resolution: golang.org/x/net - v0.0.0-20210520170846-37e1c6afe023
Parser and generator for CSS color strings
Library home page: https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/color-string/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
Regular Expression Denial of Service (ReDoS) was found in color-string before 1.5.5.
Publish Date: 2021-03-12
URL: WS-2021-0152
Base Score Metrics:
Type: Upgrade version
Release Date: 2021-03-12
Fix Resolution (color-string): 1.5.5
Direct dependency fix Resolution (winston): 3.4.0
⛑️ Automatic Remediation is available for this issue
Parser and generator for CSS color strings
Library home page: https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/color-string/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Color-String version 1.5.5 and below which occurs when the application is provided and checks a crafted invalid HWB string.
Publish Date: 2021-06-21
URL: CVE-2021-29060
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-257v-vj4p-3w2h
Release Date: 2021-06-21
Fix Resolution (color-string): 1.5.5
Direct dependency fix Resolution (winston): 3.4.0
⛑️ Automatic Remediation is available for this issue
JSON Web Almost Everything - JWA, JWS, JWE, JWK, JWT, JWKS for Node.js with minimal dependencies
Library home page: https://registry.npmjs.org/jose/-/jose-2.0.5.tgz
Path to dependency file: /juice-balancer/package.json
Path to vulnerable library: /juice-balancer/node_modules/jose/package.json,/cleaner/node_modules/jose/package.json
Dependency Hierarchy:
Found in HEAD commit: 0e0ec522551978737ae1ae4ffa66e0f7292e0fc7
Found in base branch: master
JOSE is "JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS with no dependencies using runtime's native crypto in Node.js, Browser, Cloudflare Workers, Electron, and Deno. The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named p2c
PBES2 Count, which determines how many PBKDF2 iterations must be executed in order to derive a CEK wrapping key. The purpose of this parameter is to intentionally slow down the key derivation function in order to make password brute-force and dictionary attacks more expensive. This makes the PBES2 algorithms unsuitable for situations where the JWE is coming from an untrusted source: an adversary can intentionally pick an extremely high PBES2 Count value, that will initiate a CPU-bound computation that may take an unreasonable amount of time to finish. Under certain conditions, it is possible to have the user's environment consume unreasonable amount of CPU time. The impact is limited only to users utilizing the JWE decryption APIs with symmetric secrets to decrypt JWEs from untrusted parties who do not limit the accepted JWE Key Management Algorithms (alg
Header Parameter) using the keyManagementAlgorithms
(or algorithms
in v1.x) decryption option or through other means. The v1.28.2
, v2.0.6
, v3.20.4
, and v4.9.2
releases limit the maximum PBKDF2 iteration count to 10000
by default. It is possible to adjust this limit with a newly introduced maxPBES2Count
decryption option. If users are unable to upgrade their required library version, they have two options depending on whether they expect to receive JWEs using any of the three PBKDF2-based JWE key management algorithms. They can use the keyManagementAlgorithms
decryption option to disable accepting PBKDF2 altogether, or they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (p2c
Header Parameter).
Publish Date: 2022-09-07
URL: CVE-2022-36083
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-jv3g-j58f-9mq9
Release Date: 2022-09-07
Fix Resolution (jose): 2.0.6
Direct dependency fix Resolution (@kubernetes/client-node): 0.15.0
⛑️ Automatic Remediation is available for this issue
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.