How severe is GHSA-74cp-qw7f-7hpw?

No CVSS score has been assigned to GHSA-74cp-qw7f-7hpw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-74cp-qw7f-7hpw?

GHSA-74cp-qw7f-7hpw affects the following packages: statics-server (npm). Ecosystems affected: npm.

How do I fix GHSA-74cp-qw7f-7hpw?

The records we use list no patched version of statics-server for GHSA-74cp-qw7f-7hpw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-74cp-qw7f-7hpw in my npm dependencies?

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

How do I mitigate GHSA-74cp-qw7f-7hpw 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-74cp-qw7f-7hpw actively exploited in the wild?

No public exploit code has been indexed for GHSA-74cp-qw7f-7hpw 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-74cp-qw7f-7hpw published, and has it been updated?

GHSA-74cp-qw7f-7hpw was published on June 5, 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 statics-serverGHSA-74cp-qw7f-7hpw

GHSA-74cp-qw7f-7hpw is a security vulnerability in statics-server. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Jun 5, 2019

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

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

statics-servernpm

24downloads / week

Description

All versions of statics-server are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths.

Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`statics-server`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statics-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of statics-server for GHSA-74cp-qw7f-7hpw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

All versions of `statics-server` are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-74cp-qw7f-7hpw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works