How severe is GHSA-vw7g-jq9m-3q9v?

No CVSS score has been assigned to GHSA-vw7g-jq9m-3q9v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vw7g-jq9m-3q9v?

GHSA-vw7g-jq9m-3q9v affects the following packages: glance (npm). Ecosystems affected: npm.

How do I fix GHSA-vw7g-jq9m-3q9v?

Update glance to 3.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vw7g-jq9m-3q9v is resolved across your whole dependency graph.

How do I detect GHSA-vw7g-jq9m-3q9v in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance. 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-vw7g-jq9m-3q9v 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-vw7g-jq9m-3q9v?

O3 pinpoints whether GHSA-vw7g-jq9m-3q9v 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-vw7g-jq9m-3q9v actively exploited in the wild?

No public exploit code has been indexed for GHSA-vw7g-jq9m-3q9v 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-vw7g-jq9m-3q9v published, and has it been updated?

GHSA-vw7g-jq9m-3q9v was published on September 2, 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

GHSA-vw7g-jq9m-3q9v

GHSA-vw7g-jq9m-3q9v is a security vulnerability in glance. O3 Security confirms whether GHSA-vw7g-jq9m-3q9v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Unauthorized File Access in glance

Published

Sep 2, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

glancenpm

159downloads / week

Description

Versions of glance prior to 3.0.7 are vulnerable to Unauthorized File Access. The package provides a --nodot option meant to hide files and directories with names that begin with a ., such as .git but fails to hide files inside a folder that begins with ..

Recommendation

Upgrade to version 3.0.7 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`glance`	all versions	3.0.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance. 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 glance to 3.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vw7g-jq9m-3q9v 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-vw7g-jq9m-3q9v 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-vw7g-jq9m-3q9v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `glance` prior to 3.0.7 are vulnerable to Unauthorized File Access. The package provides a `--nodot` option meant to hide files and directories with names that begin with a `.`, such as `.git` but fails to hide files inside a folder that begins with `.`. ## Recommendation Upgrade to version 3.0.7 or later.

O3 Security · Impact-Aware SCA

Is GHSA-vw7g-jq9m-3q9v in your dependencies?

O3 detects GHSA-vw7g-jq9m-3q9v 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