Vulnerable Library - firebase-6.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/grpc/node_modules/ini/package.json
Vulnerabilities
CVE |
Severity |
CVSS |
Dependency |
Type |
Fixed in (firebase version) |
Remediation Available |
CVE-2020-7768 |
Critical |
9.8 |
grpc-1.20.3.tgz |
Transitive |
7.9.1-canary.0396117e |
✅ |
CVE-2021-44906 |
Critical |
9.8 |
detected in multiple dependencies |
Transitive |
6.2.3-0 |
✅ |
CVE-2020-7788 |
Critical |
9.8 |
ini-1.3.5.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2020-7774 |
Critical |
9.8 |
y18n-3.2.1.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2021-37701 |
High |
8.6 |
tar-4.4.8.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2021-37712 |
High |
8.6 |
tar-4.4.8.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2021-37713 |
High |
8.6 |
tar-4.4.8.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2021-32804 |
High |
8.1 |
tar-4.4.8.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2021-32803 |
High |
8.1 |
tar-4.4.8.tgz |
Transitive |
6.2.3-0 |
✅ |
CVE-2022-25878 |
High |
7.5 |
detected in multiple dependencies |
Transitive |
7.9.1-canary.0396117e |
✅ |
CVE-2022-3517 |
High |
7.5 |
minimatch-3.0.4.tgz |
Transitive |
N/A* |
❌ |
CVE-2022-0235 |
Medium |
6.1 |
node-fetch-1.7.3.tgz |
Transitive |
7.9.1-canary.0396117e |
✅ |
CVE-2020-7598 |
Medium |
5.6 |
detected in multiple dependencies |
Transitive |
6.2.3-0 |
✅ |
CVE-2020-15168 |
Medium |
5.3 |
node-fetch-1.7.3.tgz |
Transitive |
7.9.1-canary.0396117e |
✅ |
CVE-2020-7765 |
Medium |
5.3 |
util-0.2.20.tgz |
Transitive |
6.2.3-canary.7043422 |
✅ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
Details
CVE-2020-7768
Vulnerable Library - grpc-1.20.3.tgz
gRPC Library for Node
Library home page: https://registry.npmjs.org/grpc/-/grpc-1.20.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/grpc/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- ❌ grpc-1.20.3.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
The package grpc before 1.24.4; the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.
Publish Date: 2020-11-11
URL: CVE-2020-7768
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7768
Release Date: 2020-11-11
Fix Resolution (grpc): 1.24.4
Direct dependency fix Resolution (firebase): 7.9.1-canary.0396117e
⛑️ Automatic Remediation is available for this issue
CVE-2021-44906
Vulnerable Libraries - minimist-1.2.0.tgz, minimist-0.0.8.tgz
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
Path to vulnerable library: /node_modules/grpc/node_modules/minimist/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- rc-1.2.8.tgz
- ❌ minimist-1.2.0.tgz (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
Path to vulnerable library: /node_modules/grpc/node_modules/mkdirp/node_modules/minimist/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- mkdirp-0.5.1.tgz
- ❌ minimist-0.0.8.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
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
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2022-03-17
Fix Resolution (minimist): 1.2.6
Direct dependency fix Resolution (firebase): 6.2.3-0
Fix Resolution (minimist): 0.2.2
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/ini/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- rc-1.2.8.tgz
- ❌ ini-1.3.5.tgz (Vulnerable Library)
Found in base branch: main
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: 2020-12-11
URL: CVE-2020-7788
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788
Release Date: 2020-12-11
Fix Resolution (ini): 1.3.6
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/y18n/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- protobufjs-5.0.3.tgz
- yargs-3.32.0.tgz
- ❌ y18n-3.2.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.
Publish Date: 2020-11-17
URL: CVE-2020-7774
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.npmjs.com/advisories/1654
Release Date: 2020-11-17
Fix Resolution (y18n): 3.2.2
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- ❌ tar-4.4.8.tgz (Vulnerable Library)
Found in base branch: main
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.
Publish Date: 2021-08-31
URL: CVE-2021-37701
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: 2021-08-31
Fix Resolution (tar): 4.4.16
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- ❌ tar-4.4.8.tgz (Vulnerable Library)
Found in base branch: main
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: 2021-08-31
URL: CVE-2021-37712
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: 2021-08-31
Fix Resolution (tar): 4.4.18
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- ❌ tar-4.4.8.tgz (Vulnerable Library)
Found in base branch: main
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.
Publish Date: 2021-08-31
URL: CVE-2021-37713
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: 2021-08-31
Fix Resolution (tar): 4.4.18
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- ❌ tar-4.4.8.tgz (Vulnerable Library)
Found in base branch: main
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.
Publish Date: 2021-08-03
URL: CVE-2021-32804
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-3jfq-g458-7qm9
Release Date: 2021-08-03
Fix Resolution (tar): 4.4.14
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- ❌ tar-4.4.8.tgz (Vulnerable Library)
Found in base branch: main
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.
Publish Date: 2021-08-03
URL: CVE-2021-32803
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-r628-mhmh-qjhw
Release Date: 2021-08-03
Fix Resolution (tar): 4.4.15
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
CVE-2022-25878
Vulnerable Libraries - protobufjs-5.0.3.tgz, protobufjs-6.8.8.tgz
protobufjs-5.0.3.tgz
Protocol Buffers for JavaScript. Finally.
Library home page: https://registry.npmjs.org/protobufjs/-/protobufjs-5.0.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/grpc/node_modules/protobufjs/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- ❌ protobufjs-5.0.3.tgz (Vulnerable Library)
protobufjs-6.8.8.tgz
Protocol Buffers for JavaScript (& TypeScript).
Library home page: https://registry.npmjs.org/protobufjs/-/protobufjs-6.8.8.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/protobufjs/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- proto-loader-0.5.1.tgz
- ❌ protobufjs-6.8.8.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
The package protobufjs before 6.11.3 are vulnerable to Prototype Pollution which can allow an attacker to add/modify properties of the Object.prototype. This vulnerability can occur in multiple ways: 1. by providing untrusted user input to util.setProperty or to ReflectionObject.setParsedOption functions 2. by parsing/loading .proto files
Publish Date: 2022-05-27
URL: CVE-2022-25878
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25878
Release Date: 2022-05-27
Fix Resolution (protobufjs): 6.10.3
Direct dependency fix Resolution (firebase): 7.9.1-canary.0396117e
Fix Resolution (protobufjs): 6.10.3
Direct dependency fix Resolution (firebase): 7.9.1-canary.0396117e
⛑️ Automatic Remediation is available for this issue
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
Path to vulnerable library: /node_modules/grpc/node_modules/minimatch/package.json,/node_modules/minimatch/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- protobufjs-5.0.3.tgz
- glob-7.1.4.tgz
- ❌ minimatch-3.0.4.tgz (Vulnerable Library)
Found in base branch: main
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: 2022-10-17
URL: CVE-2022-3517
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2022-10-17
Fix Resolution: minimatch - 3.0.5
CVE-2022-0235
Vulnerable Library - node-fetch-1.7.3.tgz
A light-weight module that brings window.fetch to node.js and io.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/node-fetch/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- functions-0.4.10.tgz
- isomorphic-fetch-2.2.1.tgz
- ❌ node-fetch-1.7.3.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Publish Date: 2022-01-16
URL: CVE-2022-0235
CVSS 3 Score Details (6.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-r683-j2x4-v87g
Release Date: 2022-01-16
Fix Resolution (node-fetch): 2.6.7
Direct dependency fix Resolution (firebase): 7.9.1-canary.0396117e
⛑️ Automatic Remediation is available for this issue
CVE-2020-7598
Vulnerable Libraries - minimist-0.0.8.tgz, minimist-1.2.0.tgz
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
Path to vulnerable library: /node_modules/grpc/node_modules/mkdirp/node_modules/minimist/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- mkdirp-0.5.1.tgz
- ❌ minimist-0.0.8.tgz (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
Path to vulnerable library: /node_modules/grpc/node_modules/minimist/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- firestore-1.4.2.tgz
- grpc-1.20.3.tgz
- node-pre-gyp-0.13.0.tgz
- rc-1.2.8.tgz
- ❌ minimist-1.2.0.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.
Publish Date: 2020-03-11
URL: CVE-2020-7598
CVSS 3 Score Details (5.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2020-03-11
Fix Resolution (minimist): 0.2.1
Direct dependency fix Resolution (firebase): 6.2.3-0
Fix Resolution (minimist): 1.2.3
Direct dependency fix Resolution (firebase): 6.2.3-0
⛑️ Automatic Remediation is available for this issue
CVE-2020-15168
Vulnerable Library - node-fetch-1.7.3.tgz
A light-weight module that brings window.fetch to node.js and io.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/node-fetch/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- functions-0.4.10.tgz
- isomorphic-fetch-2.2.1.tgz
- ❌ node-fetch-1.7.3.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
Publish Date: 2020-09-10
URL: CVE-2020-15168
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-w7rc-rwvf-8q5r
Release Date: 2020-09-17
Fix Resolution (node-fetch): 2.6.1
Direct dependency fix Resolution (firebase): 7.9.1-canary.0396117e
⛑️ Automatic Remediation is available for this issue
CVE-2020-7765
Vulnerable Library - util-0.2.20.tgz
_NOTE: This is specifically tailored for Firebase JS SDK usage, if you are not a member of the Firebase team, please avoid using this package_
Library home page: https://registry.npmjs.org/@firebase/util/-/util-0.2.20.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@firebase/util/package.json
Dependency Hierarchy:
- firebase-6.2.2.tgz (Root Library)
- ❌ util-0.2.20.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
This affects the package @firebase/util before 0.3.4. This vulnerability relates to the deepExtend function within the DeepCopy.ts file. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.
Publish Date: 2020-11-16
URL: CVE-2020-7765
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7765
Release Date: 2020-11-16
Fix Resolution (@firebase/util): 0.3.3-2020922203858
Direct dependency fix Resolution (firebase): 6.2.3-canary.7043422
⛑️ Automatic Remediation is available for this issue
⛑️ Automatic Remediation is available for this issue.