How severe is GHSA-m4vv-p6fq-jhqp?

No CVSS score has been assigned to GHSA-m4vv-p6fq-jhqp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m4vv-p6fq-jhqp?

GHSA-m4vv-p6fq-jhqp affects the following packages: @vivaxy/here (npm). Ecosystems affected: npm.

How do I fix GHSA-m4vv-p6fq-jhqp?

Update @vivaxy/here to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4vv-p6fq-jhqp is resolved across your whole dependency graph.

How do I detect GHSA-m4vv-p6fq-jhqp in my npm dependencies?

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

How do I mitigate GHSA-m4vv-p6fq-jhqp 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-m4vv-p6fq-jhqp actively exploited in the wild?

No public exploit code has been indexed for GHSA-m4vv-p6fq-jhqp 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-m4vv-p6fq-jhqp published, and has it been updated?

GHSA-m4vv-p6fq-jhqp was published on September 1, 2020 and was last updated on September 23, 2021. 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

Directory Traversal in @vivaxy/hereGHSA-m4vv-p6fq-jhqp

Fix: vivaxy/here@298dbab

GHSA-m4vv-p6fq-jhqp is a security vulnerability in @vivaxy/here. A fix is available for @vivaxy/here — see the affected versions and patch details below.

Published

Sep 1, 2020

Updated

Sep 23, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 23, 2021 · 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

@vivaxy/herenpm

102downloads / week

Description

The @vivaxy/here module is a small web server that serves files with the process' working directory acting as the web root.

It is vulnerable to a directory traversal attack.

This means that files on the local file system which exist outside of the web root may be disclosed to an attacker. This might include confidential files.

Mitigating Factors: If the node process is run as a user with very limited filesystem permissions, there is significantly less risk of exposing confidential/private information.

Proof of Concept:

curl "http://${SERVER_IP}:${SERVER_PORT}/..%2f..%2fetc/passwd"

Recommendation

Run npm i @vivaxy/here to install the latest version that addresses this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@vivaxy/here`	all versions	3.2.2`npm install @vivaxy/here@3.2.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vivaxy/here, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @vivaxy/here to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4vv-p6fq-jhqp 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

The @vivaxy/here module is a small web server that serves files with the process' working directory acting as the web root. It is vulnerable to a directory traversal attack. This means that files on the local file system which exist outside of the web root may be disclosed to an attacker. This might include confidential files. Mitigating Factors: If the node process is run as a user with very limited filesystem permissions, there is significantly less risk of exposing confidential/private information. Proof of Concept: ``` curl "http://${SERVER_IP}:${SERVER_PORT}/..%2f..%2fetc/passwd" ``

O3 Security · Impact-Aware SCA

Is GHSA-m4vv-p6fq-jhqp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works