Skip to content

[馃惛 Frogbot] Update version of lodash to 4.17.21 - #5

Open
github-actions[bot] wants to merge 1 commit into
masterfrom
frogbot-lodash-e6cfacde8f67b0ddf7c145457ad42012
Open

[馃惛 Frogbot] Update version of lodash to 4.17.21#5
github-actions[bot] wants to merge 1 commit into
masterfrom
frogbot-lodash-e6cfacde8f67b0ddf7c145457ad42012

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 1, 2025

Copy link
Copy Markdown

馃毃 This automated pull request was created by Frogbot and fixes the below:

馃摝 Vulnerable Dependencies

Severity ID Contextual Analysis Direct Dependencies Impacted Dependency Fixed Versions
critical
Critical
CVE-2019-10744 Applicable lodash:4.17.11 lodash 4.17.11 [4.17.12]

馃敄 Details

Vulnerability Details

Jfrog Research Severity: High
Contextual Analysis: Applicable
Direct Dependencies: lodash:4.17.11
Impacted Dependency: lodash:4.17.11
Fixed Versions: [4.17.12]
CVSS V3: 9.1

Insufficient input validation in lodash defaultsDeep() leads to prototype pollution.

馃敩 JFrog Research Details

Description:
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.

The function defaultsDeep was found to be vulnerable to prototype pollution, when accepting arbitrary source objects from untrusted input

Example of code vulnerable to this issue -

const lodash = require('lodash'); 
const evilsrc = {constructor: {prototype: {evilkey: "evilvalue"}}};
lodash.defaultsDeep({}, evilsrc)

Remediation:

Development mitigations

Add the Object.freeze(Object.prototype); directive once at the beginning of your main JS source code file (ex. index.js), preferably after all your require directives. This will prevent any changes to the prototype object, thus completely negating prototype pollution attacks.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant