Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-rch9-xh7r-mqgw

MEDIUMFix: senchalabs/connect@6d5dd30

GHSA-rch9-xh7r-mqgw is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in connect. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-rch9-xh7r-mqgw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in connect

Also known asCVE-2018-3717
Published
Jul 26, 2018
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, 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.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
connectnpm
19.7Mdownloads / week

Description

connect node module before 2.14.0 suffers from a Cross-Site Scripting (XSS) vulnerability due to a lack of validation of file in directory.js middleware.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmconnectall versions2.14.0
Exploits & PoCs
2

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 connect. 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 connect to 2.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rch9-xh7r-mqgw 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-rch9-xh7r-mqgw 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-rch9-xh7r-mqgw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

connect node module before 2.14.0 suffers from a Cross-Site Scripting (XSS) vulnerability due to a lack of validation of file in directory.js middleware.
O3 Security · Impact-Aware SCA

Is GHSA-rch9-xh7r-mqgw in your dependencies?

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

GHSA-rch9-xh7r-mqgw: Cross-Site Scripting… | O3 Security