You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Path to vulnerable library: /node_modules/protobufjs/package.json
Dependency Hierarchy:
firebase-9.11.0.tgz (Root Library)
@firebase/firestore-3.6.0.tgz
proto-loader-0.6.13.tgz
❌ protobufjs-6.11.3.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
"protobuf.js (aka protobufjs) 6.10.0 through 7.x before 7.2.5 allows Prototype Pollution, a different vulnerability than CVE-2022-25878. A user-controlled protobuf message can be used by an attacker to pollute the prototype of Object.prototype by adding and overwriting its data and functions. Exploitation can involve: (1) using the function parse to parse protobuf messages on the fly, (2) loading .proto files by using load/loadSync functions, or (3) providing untrusted input to the functions ReflectionObject.setParsedOption and util.setProperty.
Path to vulnerable library: /node_modules/ws/package.json
Dependency Hierarchy:
firebase-9.11.0.tgz (Root Library)
@firebase/auth-0.20.8.tgz
selenium-webdriver-4.1.2.tgz
❌ ws-8.9.0.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
Path to vulnerable library: /node_modules/@grpc/grpc-js/package.json
Dependency Hierarchy:
firebase-9.11.0.tgz (Root Library)
@firebase/firestore-3.6.0.tgz
❌ grpc-js-1.7.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to versions 1.10.9, 1.9.15, and 1.8.22, there are two separate code paths in which memory can be allocated per message in excess of the grpc.max_receive_message_length channel option: If an incoming message has a size on the wire greater than the configured limit, the entire message is buffered before it is discarded; and/or if an incoming message has a size within the limit on the wire but decompresses to a size greater than the limit, the entire message is decompressed into memory, and on the server is not discarded. This has been patched in versions 1.10.9, 1.9.15, and 1.8.22.
Path to vulnerable library: /node_modules/@firebase/auth/package.json
Dependency Hierarchy:
firebase-9.11.0.tgz (Root Library)
❌ @firebase/auth-0.20.8.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
Firebase JavaScript SDK utilizes a "FIREBASE_DEFAULTS" cookie to store configuration data, including an "_authTokenSyncURL" field used for session synchronization. If this cookie field is preset via an attacker by any other method, the attacker can manipulate the "_authTokenSyncURL" to point to their own server and it would allow an actor to capture user session data transmitted by the SDK. We recommend upgrading Firebase JS SDK at least to 10.9.0.
mend-for-github-combot
changed the title
firebase-9.11.0.tgz: 1 vulnerabilities (highest severity is: 9.8)
firebase-9.11.0.tgz: 2 vulnerabilities (highest severity is: 9.8)
Jun 19, 2024
mend-for-github-combot
changed the title
firebase-9.11.0.tgz: 2 vulnerabilities (highest severity is: 9.8)
firebase-9.11.0.tgz: 3 vulnerabilities (highest severity is: 9.8)
Jun 19, 2024
mend-for-github-combot
changed the title
firebase-9.11.0.tgz: 3 vulnerabilities (highest severity is: 9.8)
firebase-9.11.0.tgz: 4 vulnerabilities (highest severity is: 9.8)
Nov 18, 2024
Vulnerable Library - firebase-9.11.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@grpc/grpc-js/package.json
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2023-36665
Vulnerable Libraries - protobufjs-7.1.2.tgz, protobufjs-6.11.3.tgz
protobufjs-7.1.2.tgz
Protocol Buffers for JavaScript (& TypeScript).
Library home page: https://registry.npmjs.org/protobufjs/-/protobufjs-7.1.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@grpc/grpc-js/node_modules/protobufjs/package.json
Dependency Hierarchy:
protobufjs-6.11.3.tgz
Protocol Buffers for JavaScript (& TypeScript).
Library home page: https://registry.npmjs.org/protobufjs/-/protobufjs-6.11.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/protobufjs/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
"protobuf.js (aka protobufjs) 6.10.0 through 7.x before 7.2.5 allows Prototype Pollution, a different vulnerability than CVE-2022-25878. A user-controlled protobuf message can be used by an attacker to pollute the prototype of Object.prototype by adding and overwriting its data and functions. Exploitation can involve: (1) using the function parse to parse protobuf messages on the fly, (2) loading .proto files by using load/loadSync functions, or (3) providing untrusted input to the functions ReflectionObject.setParsedOption and util.setProperty.
Publish Date: 2023-07-05
URL: CVE-2023-36665
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2023-36665
Release Date: 2023-07-05
Fix Resolution (protobufjs): 7.2.5
Direct dependency fix Resolution (firebase): 9.12.0-20221010190246
Fix Resolution (protobufjs): 7.2.5
Direct dependency fix Resolution (firebase): 9.12.0-20221010190246
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-37890
Vulnerable Library - ws-8.9.0.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-8.9.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/ws/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
Publish Date: 2024-06-17
URL: CVE-2024-37890
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution (ws): 8.17.1
Direct dependency fix Resolution (firebase): 9.12.0-20221010190246
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-37168
Vulnerable Library - grpc-js-1.7.1.tgz
gRPC Library for Node - pure JS implementation
Library home page: https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-1.7.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@grpc/grpc-js/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to versions 1.10.9, 1.9.15, and 1.8.22, there are two separate code paths in which memory can be allocated per message in excess of the
grpc.max_receive_message_length
channel option: If an incoming message has a size on the wire greater than the configured limit, the entire message is buffered before it is discarded; and/or if an incoming message has a size within the limit on the wire but decompresses to a size greater than the limit, the entire message is decompressed into memory, and on the server is not discarded. This has been patched in versions 1.10.9, 1.9.15, and 1.8.22.Publish Date: 2024-06-10
URL: CVE-2024-37168
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-7v5v-9h63-cj86
Release Date: 2024-06-10
Fix Resolution (@grpc/grpc-js): 1.8.22
Direct dependency fix Resolution (firebase): 9.12.0-20221010190246
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-11023
Vulnerable Library - @firebase/auth-0.20.8.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@firebase/auth/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Firebase JavaScript SDK utilizes a "FIREBASE_DEFAULTS" cookie to store configuration data, including an "_authTokenSyncURL" field used for session synchronization. If this cookie field is preset via an attacker by any other method, the attacker can manipulate the "_authTokenSyncURL" to point to their own server and it would allow an actor to capture user session data transmitted by the SDK. We recommend upgrading Firebase JS SDK at least to 10.9.0.
Publish Date: 2024-11-18
URL: CVE-2024-11023
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Release Date: 2024-11-18
Fix Resolution: @firebase/auth - 1.6.2
⛑️Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: