Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-q2qh-cgc2-qhr3

MEDIUM

Directory Traversal in serve

Also known asCVE-2018-3712
Published
Jul 27, 2018
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected

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

servenpm
3.9Mdownloads / week

Description

Affected versions of serve do not properly handle %2e (.) and %2f (/) characters, and allow the, characters to be used in paths. This can be used to traverse the directory tree and list content of any directory the user running the process has access to.

Mitigating factors: This vulnerability only allows listing of directory contents and does not allow reading of arbitrary files.

Recommendation

Update to version 6.4.9 later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmserveall versions6.4.9
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serve. 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.

  2. Fix

    Update serve to 6.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q2qh-cgc2-qhr3 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-q2qh-cgc2-qhr3 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-q2qh-cgc2-qhr3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `serve` do not properly handle `%2e` (.) and `%2f` (/) characters, and allow the, characters to be used in paths. This can be used to traverse the directory tree and list content of any directory the user running the process has access to. Mitigating factors: This vulnerability only allows listing of directory contents and does not allow reading of arbitrary files. ## Recommendation Update to version 6.4.9 later.
O3 Security · Impact-Aware SCA

Is GHSA-q2qh-cgc2-qhr3 in your dependencies?

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