Dns Sync

Vendor:

First CVE: Feb 28, 2015 · Active for 11 years

2
Total CVEs
More Total CVEs than 49% of tracked products
1.0
Avg CVEs / Year
Bottom 1%
9.9
Avg CVSS
Higher Avg CVSS than 99% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Dns Sync over time

Volume of CVEsAvg CVSS Base Score
First CVE
Feb 28, 2015
11 years ago
Most Recent CVE
Jun 7, 2018
2,970 days ago

CVE Severity & Scoring

Dns Sync2 CVEs
All CVEs352,294 CVEs
HighCritical
Attack Vector
Local0 (0.0%)
Network1 (50.0%)
Unknown1 (50.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (50.0%)
High0 (0.0%)
Unknown1 (50.0%)
User Interaction
None1 (50.0%)
Unknown1 (50.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (50.0%)
Unknown1 (50.0%)

Top CVEs

Signals from CVEs in this product scope (2 CVEs).

2 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
The dns-sync module before 0.1.1 for node.js allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the first argument to the resolve API func
Feb 28, 201510.030NONO
dns-sync is a sync/blocking dns resolver. If untrusted user input is allowed into the resolve() method then command injection is possible.
Jun 7, 20189.827NONO

Exploit Exposure

Signals from CVEs in this product scope (2 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (2 CVEs).

Media Mentions

Signals from CVEs in this product scope (2 CVEs).

Top CNAs Publishing CVEs For Dns Sync

Top CWEs

Versions

No cataloged versions.