How severe is GHSA-4qqc-mp5f-ccv4?

No CVSS score has been assigned to GHSA-4qqc-mp5f-ccv4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4qqc-mp5f-ccv4?

GHSA-4qqc-mp5f-ccv4 affects the following packages: bestzip (npm). Ecosystems affected: npm.

How do I fix GHSA-4qqc-mp5f-ccv4?

Update bestzip to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4qqc-mp5f-ccv4 is resolved across your whole dependency graph.

How do I detect GHSA-4qqc-mp5f-ccv4 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bestzip, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4qqc-mp5f-ccv4 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-4qqc-mp5f-ccv4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4qqc-mp5f-ccv4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4qqc-mp5f-ccv4 published, and has it been updated?

GHSA-4qqc-mp5f-ccv4 was published on September 2, 2020 and was last updated on September 2, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Command Injection in bestzipGHSA-4qqc-mp5f-ccv4

GHSA-4qqc-mp5f-ccv4 is a remote code execution vulnerability in bestzip. A fix is available for bestzip — see the affected versions and patch details below.

Published

Sep 2, 2020

Updated

Sep 2, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 2, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

71other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

bestzipnpm

501Kdownloads / week

Description

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' })

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`bestzip`	all versions	2.1.7`npm install bestzip@2.1.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bestzip, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bestzip to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4qqc-mp5f-ccv4 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

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' })`

O3 Security · Impact-Aware SCA

Is GHSA-4qqc-mp5f-ccv4 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works