Summary
Command Injection in dns-sync
Affected versions of dns-sync have an arbitrary command execution vulnerability in the resolve() method.
Impact
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Use an alternative dns resolver
- Do not allow untrusted input into
dns-sync.resolve()
Frequently Asked Questions
- What is CVE-2017-16100? CVE-2017-16100 is a critical-severity code injection vulnerability in dns-sync (npm), affecting versions < 0.1.1. It is fixed in 0.1.1. Untrusted input is evaluated as executable code within the application's runtime environment.
- Which versions of dns-sync are affected by CVE-2017-16100? dns-sync (npm) versions < 0.1.1 is affected.
- Is there a fix for CVE-2017-16100? Yes. CVE-2017-16100 is fixed in 0.1.1. Upgrade to this version or later.
- Is CVE-2017-16100 exploitable, and should I be worried? Whether CVE-2017-16100 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2017-16100 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2017-16100? Upgrade
dns-syncto 0.1.1 or later.