Skip to content
Fencer Intel
critical 9.8

CVE-2017-16100 json

Command Injection in dns-sync

published 2018-06-07 8 y ago modified 2026-06-17 4 mo ago also GHSA-jcw8-r9xm-32c6 , EUVD-2018-0287

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.1%
EPSS 5.1% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

dns-sync is a sync/blocking dns resolver. If untrusted user input is allowed into the resolve() method then command injection is possible.

Patch / fix

  • npm dns-sync 0.1.1

Exploit prediction

5.05% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/skoranga/node-dns-sync/issues/5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected packages

ecosystem package affected fixed in
npm dns-sync
<0.1.1
0.1.1

Affected products

  • HackerOne dns-sync node module

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.