artkamote / examples

Serverless Examples – A collection of boilerplates and examples of serverless architectures built with the Serverless Framework on AWS Lambda, Microsoft Azure, Google Cloud Functions, and more.
https://www.serverless.com/examples/
Other
0 stars 0 forks source link

CVE-2019-10747 (Critical) detected in multiple libraries #99

Open mend-bolt-for-github[bot] opened 2 years ago

mend-bolt-for-github[bot] commented 2 years ago

CVE-2019-10747 - Critical Severity Vulnerability

Vulnerable Libraries - set-value-3.0.0.tgz, set-value-0.4.3.tgz, set-value-2.0.0.tgz

set-value-3.0.0.tgz

Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.

Library home page: https://registry.npmjs.org/set-value/-/set-value-3.0.0.tgz

Path to dependency file: /aws-node-fullstack/backend/package.json

Path to vulnerable library: /aws-node-fullstack/backend/node_modules/set-value/package.json

Dependency Hierarchy: - serverless-finch-2.4.2.tgz (Root Library) - prompt-confirm-1.2.0.tgz - prompt-base-4.1.0.tgz - prompt-question-5.0.2.tgz - prompt-choices-4.1.0.tgz - :x: **set-value-3.0.0.tgz** (Vulnerable Library)

set-value-0.4.3.tgz

Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.

Library home page: https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz

Path to dependency file: /aws-node-fullstack/frontend/package.json

Path to vulnerable library: /aws-node-fullstack/frontend/node_modules/union-value/node_modules/set-value/package.json,/aws-node-github-check/node_modules/union-value/node_modules/set-value/package.json,/aws-node-typescript-nest/node_modules/union-value/node_modules/set-value/package.json

Dependency Hierarchy: - react-scripts-2.1.8.tgz (Root Library) - webpack-4.28.3.tgz - micromatch-3.1.10.tgz - snapdragon-0.8.2.tgz - base-0.11.2.tgz - cache-base-1.0.1.tgz - union-value-1.0.0.tgz - :x: **set-value-0.4.3.tgz** (Vulnerable Library)

set-value-2.0.0.tgz

Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.

Library home page: https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz

Path to dependency file: /aws-node-github-check/package.json

Path to vulnerable library: /aws-node-github-check/node_modules/set-value/package.json,/aws-node-typescript-nest/node_modules/set-value/package.json,/aws-node-fullstack/frontend/node_modules/set-value/package.json

Dependency Hierarchy: - react-scripts-2.1.8.tgz (Root Library) - webpack-4.28.3.tgz - micromatch-3.1.10.tgz - snapdragon-0.8.2.tgz - base-0.11.2.tgz - cache-base-1.0.1.tgz - :x: **set-value-2.0.0.tgz** (Vulnerable Library)

Found in HEAD commit: dcbe4aefe4b3685f4b15493a01db0f19b118a0c4

Found in base branch: master

Vulnerability Details

set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.

Publish Date: 2019-08-23

URL: CVE-2019-10747

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: 2019-08-23

Fix Resolution (set-value): 3.0.1

Direct dependency fix Resolution (serverless-finch): 2.4.3

Fix Resolution (set-value): 3.0.1

Direct dependency fix Resolution (react-scripts): 3.0.0

Fix Resolution (set-value): 3.0.1

Direct dependency fix Resolution (react-scripts): 3.0.0


Step up your Open Source Security Game with Mend here

mend-bolt-for-github[bot] commented 3 months ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

mend-bolt-for-github[bot] commented 3 months ago

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.