Critical
Command Injection in dns-sync
Affected versions of dns-sync have an arbitrary command execution vulnerability in the resolve() method.
Recommendation
- Use an alternative dns resolver
- Do not allow untrusted input into
dns-sync.resolve()
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | dns-sync | < 0.1.1 | 0.1.1 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2017-16100
- https://github.com/skoranga/node-dns-sync/issues/1
- https://github.com/skoranga/node-dns-sync/issues/1)
- https://github.com/skoranga/node-dns-sync/issues/5
- https://github.com/skoranga/node-dns-sync/commit/d9abaae384b198db1095735ad9c1c73d7b890a0d
- https://github.com/skoranga/node-dns-sync/commit/d9abaae384b198db1095735ad9c1c73d7b890a0d)))
- https://github.com/advisories/GHSA-jcw8-r9xm-32c6
- https://www.npmjs.com/advisories/153
- https://www.npmjs.com/advisories/523
CVSS score
-
- Weakness (CWE)
CWE-94- Platform
- npm
- Package
dns-sync- Disclosed
- 18.07.2018
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-jcw8-r9xm-32c6 - CC BY 4.0
Vulnerability history: dns-sync
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 3
- First → latest
- 10.2017 05.2020
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 2
- High 1
Disclosures per year
- 2017: 1
- 2018: 1
- 2019: 0
- 2020: 1
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Command Injection in dns-sync this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.