AlexRogalskiy / java-patterns

🏆 Java4You Design patterns
https://alexander-rogalsky.gitbook.io/java-patterns/
GNU General Public License v3.0
11 stars 4 forks source link

CVE-2019-10744 (High) detected in lodash-2.4.2.tgz #462

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

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

CVE-2019-10744 - High Severity Vulnerability

Vulnerable Library - lodash-2.4.2.tgz

A utility library delivering consistency, customization, performance, & extras.

Library home page: https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz

Path to dependency file: java-patterns/package.json

Path to vulnerable library: java-patterns/node_modules/dockerfile_lint/node_modules/lodash/package.json

Dependency Hierarchy: - dockerfile_lint-0.3.4.tgz (Root Library) - :x: **lodash-2.4.2.tgz** (Vulnerable Library)

Found in HEAD commit: 8bad729c83be710b20cd3f2d4defd1f1f0ebb100

Found in base branch: master

Vulnerability Details

Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

Publish Date: 2019-07-26

URL: CVE-2019-10744

CVSS 3 Score Details (9.1)

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: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-jf85-cpcp-j695

Release Date: 2019-07-08

Fix Resolution: lodash-4.17.12, lodash-amd-4.17.12, lodash-es-4.17.12, lodash.defaultsdeep-4.6.1, lodash.merge- 4.6.2, lodash.mergewith-4.6.2, lodash.template-4.5.0


Step up your Open Source Security Game with WhiteSource here

github-actions[bot] commented 3 years ago

👋 Thanks for reporting!

github-actions[bot] commented 2 years ago

Greetings! Sorry to say but this is a very old issue that is probably not getting as much attention as it deservers. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.