Skip to content

pydash Command Injection vulnerability

High severity GitHub Reviewed Published Sep 28, 2023 to the GitHub Advisory Database • Updated Nov 7, 2023

Package

pip pydash (pip)

Affected versions

< 6.0.0

Patched versions

6.0.0

Description

This affects versions of the package pydash before 6.0.0. A number of pydash methods such as pydash.objects.invoke() and pydash.collections.invoke_map() accept dotted paths (Deep Path Strings) to target a nested Python object, relative to the original source object. These paths can be used to target internal class attributes and dict items, to retrieve, modify or invoke nested Python objects.

Note:

The pydash.objects.invoke() method is vulnerable to Command Injection when the following prerequisites are satisfied:

  1. The source object (argument 1) is not a built-in object such as list/dict (otherwise, the init.globals path is not accessible)

  2. The attacker has control over argument 2 (the path string) and argument 3 (the argument to pass to the invoked method)

The pydash.collections.invoke_map() method is also vulnerable, but is harder to exploit as the attacker does not have direct control over the argument to be passed to the invoked function.

References

Published by the National Vulnerability Database Sep 28, 2023
Published to the GitHub Advisory Database Sep 28, 2023
Reviewed Sep 28, 2023
Last updated Nov 7, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.076%
(33rd percentile)

Weaknesses

CVE ID

CVE-2023-26145

GHSA ID

GHSA-8mjr-6c96-39w8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.