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

GHSA-wh69-wc6q-7888

HIGHFix: skoranga/node-dns-sync@cb10a5a

GHSA-wh69-wc6q-7888 is a high-severity (CVSS 8.6) Code Injection vulnerability in dns-sync. O3 Security confirms whether GHSA-wh69-wc6q-7888 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Command injection in node-dns-sync

Also known asCVE-2020-11079
Published
May 28, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · 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.

21other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
dns-syncnpm
4Kdownloads / week

Description

dns-sync through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdns-sync0.1.3&&< 0.2.10.2.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dns-sync. 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 dns-sync to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wh69-wc6q-7888 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-wh69-wc6q-7888 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-wh69-wc6q-7888. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

dns-sync through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.
O3 Security · Impact-Aware SCA

Is GHSA-wh69-wc6q-7888 in your dependencies?

O3 detects GHSA-wh69-wc6q-7888 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-wh69-wc6q-7888: Command injection… | O3 Security