node-chromedriver up to 119.0.0 Setting chromedriver.path os command injection

Summaryinfo

A vulnerability was found in node-chromedriver up to 119.0.0 and classified as critical. This issue affects some unknown processing of the component Setting Handler. Executing a manipulation of the argument chromedriver.path can lead to os command injection. The identification of this vulnerability is CVE-2023-26156. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in node-chromedriver up to 119.0.0 (Hardware Driver Software). This vulnerability affects an unknown code of the component Setting Handler. The manipulation of the argument chromedriver.path with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Versions of the package chromedriver before 119.0.1 are vulnerable to Command Injection when setting the chromedriver.path to an arbitrary system binary. This could lead to unauthorized access and potentially malicious actions on the host system. **Note:** An attacker must have access to the system running the vulnerable chromedriver library to exploit it. The success of exploitation also depends on the permissions and privileges of the process running chromedriver.

The weakness was shared 11/09/2023 as de961e34e023afcf4fa5c0faeeec69aaa6c3c815. The advisory is shared for download at github.com. This vulnerability was named CVE-2023-26156 since 02/20/2023. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1202.

Upgrading to version 119.0.1 eliminates this vulnerability. Applying the patch de961e34e023afcf4fa5c0faeeec69aaa6c3c815 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Hardware Driver Software

Name

• node-chromedriver

Version

• 119.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion