Skip to content

← Public intelligence

npm package

bestzip

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. Critical, CVSS 9.8npmAmendedPublished

    Command injection in bestzip

    CVE-2020-7730 · GHSA-6xv6-jpvw-cx6q

    Affected
    • npm bestzip < 2.1.7
    Fixed in
    2.1.7· Vendor fix available
    Issue
    The package bestzip before 2.1.7 are vulnerable to Command Injection via the options param.

    Recommended action: Upgrade to 2.1.7 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. UnratednpmAmendedPublished

    Command Injection in bestzip

    GHSA-4qqc-mp5f-ccv4

    Affected
    • npm bestzip < 2.1.7
    Fixed in
    2.1.7· Vendor fix available
    Issue
    Versions of bestzip prior to 2.1.7 are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an exec call on the zip function . This may allow attackers to execute arbitrary code in the system as long as the values of destination is user-controlled. This only affects users with a native zip command available. The following examples demonstrate the issue from the CLI and also programatically: - bestzip test.zip 'sourcefile; mkdir folder' - zip({ source: 'sourcefile', destination: './test.zip; mkdir folder' })

    Recommended action: Upgrade to 2.1.7 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 →