GHSA-6wcc-39rp-hh9p
CRITICALGHSA-6wcc-39rp-hh9p is a critical-severity (CVSS 9.8) SQL Injection vulnerability in @hypequery/clickhouse. O3 Security confirms whether GHSA-6wcc-39rp-hh9p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
@hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution
Blast Radius
@hypequery/clickhouseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A SQL injection vulnerability exists in the escapeValue() function used for parameter substitution. Attackers who can control parameter values can inject arbitrary SQL by using a trailing backslash to escape the closing quote.
Who is impacted: All users of @hypequery/clickhouse versions prior to 2.0.2 who pass user-controlled input as query parameters.
Patches
The vulnerability has been patched in version 2.0.2. The fix properly escapes backslashes before escaping single quotes
Workarounds
No workaround exists other than upgrading. Manual input validation/sanitization is not recommended as a mitigation - the library must handle escaping correctly.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @hypequery/clickhouse | all versions | 2.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hypequery/clickhouse. 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 @hypequery/clickhouse to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wcc-39rp-hh9p 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-6wcc-39rp-hh9p 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-6wcc-39rp-hh9p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6wcc-39rp-hh9p in your dependencies?
O3 detects GHSA-6wcc-39rp-hh9p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.