How severe is GHSA-crf7-fvjx-863q?

No CVSS score has been assigned to GHSA-crf7-fvjx-863q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-crf7-fvjx-863q?

GHSA-crf7-fvjx-863q affects the following packages: zero (npm). Ecosystems affected: npm.

How do I fix GHSA-crf7-fvjx-863q?

Update zero to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-crf7-fvjx-863q is resolved across your whole dependency graph.

How do I detect GHSA-crf7-fvjx-863q in my npm dependencies?

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

How do I mitigate GHSA-crf7-fvjx-863q if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-crf7-fvjx-863q actively exploited in the wild?

No public exploit code has been indexed for GHSA-crf7-fvjx-863q 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-crf7-fvjx-863q published, and has it been updated?

GHSA-crf7-fvjx-863q was published on September 3, 2020 and was last updated on August 31, 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

Path Traversal in zeroGHSA-crf7-fvjx-863q

GHSA-crf7-fvjx-863q is a security vulnerability in zero. A fix is available for zero — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 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.

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

zeronpm

537downloads / week

Description

Versions of zero prior to 1.0.6 are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files.

Recommendation

Upgrade to version 1.0.6 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`zero`	all versions	1.0.6`npm install zero@1.0.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zero, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zero to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-crf7-fvjx-863q is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Versions of `zero` prior to 1.0.6 are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. ## Recommendation Upgrade to version 1.0.6 or later.

O3 Security · Impact-Aware SCA

Is GHSA-crf7-fvjx-863q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works