This project uses Node, React, Google Translate and Nexmo to create a real-time SMS translation demo application. Using a websocket, incoming text messages are sent to Google Translate API and then forwarded to the front-end application for display.
MIT License
1
stars
1
forks
source link
translate-5.1.4.tgz: 6 vulnerabilities (highest severity is: 8.2) #12
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
Path to vulnerable library: /node_modules/teeny-request/node_modules/node-fetch/package.json,/node_modules/google-gax/node_modules/node-fetch/package.json,/node_modules/gaxios/node_modules/node-fetch/package.json
@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/teeny-request/node_modules/node-fetch/package.json,/node_modules/google-gax/node_modules/node-fetch/package.json,/node_modules/gaxios/node_modules/node-fetch/package.json
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.
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@grpc/grpc-js/package.json
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2022-25878
### Vulnerable Library - protobufjs-6.8.8.tgzProtocol 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: - translate-5.1.4.tgz (Root Library) - :x: **protobufjs-6.8.8.tgz** (Vulnerable Library)
Found in base branch: main
### Vulnerability DetailsThe 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 (8.2)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: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: 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 (@google-cloud/translate): 5.1.5
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2020-8237
### Vulnerable Library - json-bigint-0.3.0.tgzJSON.parse with bigints support
Library home page: https://registry.npmjs.org/json-bigint/-/json-bigint-0.3.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/json-bigint/package.json
Dependency Hierarchy: - translate-5.1.4.tgz (Root Library) - common-2.3.0.tgz - google-auth-library-5.9.2.tgz - gcp-metadata-3.3.0.tgz - :x: **json-bigint-0.3.0.tgz** (Vulnerable Library)
Found in base branch: main
### Vulnerability DetailsPrototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.
Publish Date: 2020-09-18
URL: CVE-2020-8237
### 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 FixType: Upgrade version
Origin: https://hackerone.com/reports/916430
Release Date: 2020-09-30
Fix Resolution (json-bigint): 1.0.0
Direct dependency fix Resolution (@google-cloud/translate): 6.0.0
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2020-7768
### Vulnerable Library - grpc-js-0.6.15.tgzgRPC Library for Node - pure JS implementation
Library home page: https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-0.6.15.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@grpc/grpc-js/package.json
Dependency Hierarchy: - translate-5.1.4.tgz (Root Library) - google-gax-1.14.1.tgz - :x: **grpc-js-0.6.15.tgz** (Vulnerable Library)
Found in base branch: main
### Vulnerability DetailsThe 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 (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 FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7768
Release Date: 2020-11-11
Fix Resolution (@grpc/grpc-js): 1.1.8
Direct dependency fix Resolution (@google-cloud/translate): 5.1.5
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2022-0235
### Vulnerable Library - node-fetch-2.6.0.tgzA light-weight module that brings window.fetch to node.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/teeny-request/node_modules/node-fetch/package.json,/node_modules/google-gax/node_modules/node-fetch/package.json,/node_modules/gaxios/node_modules/node-fetch/package.json
Dependency Hierarchy: - translate-5.1.4.tgz (Root Library) - google-gax-1.14.1.tgz - :x: **node-fetch-2.6.0.tgz** (Vulnerable Library)
Found in base branch: main
### Vulnerability Detailsnode-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 FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-r683-j2x4-v87g
Release Date: 2022-01-16
Fix Resolution (node-fetch): 2.6.7
Direct dependency fix Resolution (@google-cloud/translate): 5.1.5
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2024-37168
### Vulnerable Library - grpc-js-0.6.15.tgzgRPC Library for Node - pure JS implementation
Library home page: https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-0.6.15.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@grpc/grpc-js/package.json
Dependency Hierarchy: - translate-5.1.4.tgz (Root Library) - google-gax-1.14.1.tgz - :x: **grpc-js-0.6.15.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.
Publish Date: 2024-06-10
URL: CVE-2024-37168
### 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 FixType: Upgrade version
Origin: https://github.com/grpc/grpc-node/security/advisories/GHSA-7v5v-9h63-cj86
Release Date: 2024-06-10
Fix Resolution (@grpc/grpc-js): 1.8.22
Direct dependency fix Resolution (@google-cloud/translate): 7.0.0
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2020-15168
### Vulnerable Library - node-fetch-2.6.0.tgzA light-weight module that brings window.fetch to node.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/teeny-request/node_modules/node-fetch/package.json,/node_modules/google-gax/node_modules/node-fetch/package.json,/node_modules/gaxios/node_modules/node-fetch/package.json
Dependency Hierarchy: - translate-5.1.4.tgz (Root Library) - google-gax-1.14.1.tgz - :x: **node-fetch-2.6.0.tgz** (Vulnerable Library)
Found in base branch: main
### Vulnerability Detailsnode-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 (2.6)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
Release Date: 2020-09-17
Fix Resolution (node-fetch): 2.6.1
Direct dependency fix Resolution (@google-cloud/translate): 5.1.5
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.