How severe is GHSA-rv49-54qp-fw42?

No CVSS score has been assigned to GHSA-rv49-54qp-fw42 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rv49-54qp-fw42?

GHSA-rv49-54qp-fw42 affects the following packages: servey (npm). Ecosystems affected: npm.

How do I fix GHSA-rv49-54qp-fw42?

Update servey to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rv49-54qp-fw42 is resolved across your whole dependency graph.

How do I detect GHSA-rv49-54qp-fw42 in my npm dependencies?

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

How do I mitigate GHSA-rv49-54qp-fw42 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-rv49-54qp-fw42 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rv49-54qp-fw42 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-rv49-54qp-fw42 published, and has it been updated?

GHSA-rv49-54qp-fw42 was published on June 6, 2019 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 serveyGHSA-rv49-54qp-fw42

Fix: typeorm/typeorm@d46c8b0

GHSA-rv49-54qp-fw42 is a security vulnerability in servey. A fix is available for servey — see the affected versions and patch details below.

Published

Jun 6, 2019

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.

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

serveynpm

161downloads / week

Description

Versions of servey prior to 3.x are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths.

Recommendation

Upgrade to the latest version

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`servey`	all versions	3.1.0`npm install servey@3.1.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for servey, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update servey to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rv49-54qp-fw42 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 `servey` prior to 3.x are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths. ## Recommendation Upgrade to the latest version

O3 Security · Impact-Aware SCA

Is GHSA-rv49-54qp-fw42 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works