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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m4vv-p6fq-jhqp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m4vv-p6fq-jhqp?

O3 pinpoints whether GHSA-m4vv-p6fq-jhqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-m4vv-p6fq-jhqp

Fix: vivaxy/here@298dbab

GHSA-m4vv-p6fq-jhqp is a security vulnerability in @vivaxy/here. O3 Security confirms whether GHSA-m4vv-p6fq-jhqp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Directory Traversal in @vivaxy/here

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

📦@vivaxy/here

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m4vv-p6fq-jhqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m4vv-p6fq-jhqp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-m4vv-p6fq-jhqp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works