CVE-2020-11079: node-dns-sync (npm module dns-sync) through 0.2.0 allows execution of arbitrary commands

Q: How do I fix CVE-2020-11079?

node-dns-sync: upgrade to 0.2.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-11079 being exploited?

CVE-2020-11079 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-11079 affect?

CVE-2020-11079 affects node-dns-sync. Severity is high (CVSS 8.6). node-dns-sync (npm module 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. This has been fixed in 0.2.

Q: How urgent is CVE-2020-11079?

Priority 57/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.6REMOTEUPGRADE

CVE-2020-11079 is a high-severity flaw (CVSS 8.6) affecting node-dns-sync. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

node-dns-sync (npm module 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. This has been fixed in 0.2.1.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.7% (top 14%)
CISA exploited list	No
Weakness	CWE-94, CWE-77
Published	2020-05-28
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: node-dns-sync project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-05-28 19:15 UTCPublished CVE record published
2026-06-17 02:49 UTCUpdated Record last modified

node-dns-sync project node-dns-sync UPGRADE

Affected: < 0.2.1

Fixed in: 0.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy node-dns-sync || rpm -q node-dns-sync || node-dns-sync --version

2. UPGRADE to 0.2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade node-dns-sync

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade node-dns-sync

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-11079?

node-dns-sync: upgrade to 0.2.1. Exact commands for each OS are on this page.

Is CVE-2020-11079 being exploited?

CVE-2020-11079 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-11079 affect?

CVE-2020-11079 affects node-dns-sync. Severity is high (CVSS 8.6). node-dns-sync (npm module 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. This has been fixed in 0.2.

How urgent is CVE-2020-11079?

Priority 57/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs