Skip to content

← Public intelligence

npm package

chromedriver

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.6npmAmendedPublished

    chromedriver Command Injection vulnerability

    CVE-2023-26156 · GHSA-hm92-vgmw-qfmx

    Affected
    • npm chromedriver < 119.0.1
    Fixed in
    119.0.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 119.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.1npmAmendedPublished

    chromedriver Downloads Resources over HTTP

    CVE-2016-10579 · GHSA-jh5w-6964-x5cf

    Affected
    • npm chromedriver < 2.25.2
    Fixed in
    2.25.2· Vendor fix available
    Issue
    Affected versions of chromedriver insecurely download resources over HTTP. In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This may result in arbitrary code execution if an attacker intercepts and modifies the downloaded binary file, replacing it with a malicious one. Recommendation Update to version 2.26.1 or later.

    Recommended action: Upgrade to 2.25.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →