First published: Sat Jan 21 2006(Updated: )
Unspecified "critical denial-of-service vulnerability" in MyDNS before 1.1.0 has unknown impact and attack vectors.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
myDNS | =0.6 | |
myDNS | =0.7 | |
myDNS | =0.7.1 | |
myDNS | =0.8 | |
myDNS | =0.8.1 | |
myDNS | =0.8.2 | |
myDNS | =0.8.3 | |
myDNS | =0.9.0 | |
myDNS | =0.9.1 | |
myDNS | =0.9.2 | |
myDNS | =0.9.3 | |
myDNS | =0.9.5 | |
myDNS | =0.9.6 | |
myDNS | =0.9.7 | |
myDNS | =0.9.8 | |
myDNS | =0.9.9 | |
myDNS | =0.9.10 | |
myDNS | =0.9.12 | |
myDNS | =0.9.13 | |
myDNS | =0.10.0 | |
myDNS | =0.10.1 | |
myDNS | =0.10.2 | |
myDNS | =0.10.3 | |
myDNS | =0.10.4 | |
myDNS | =0.11.0 | |
myDNS | =1.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2006-0351 is classified as a critical denial-of-service vulnerability.
To resolve CVE-2006-0351, upgrade your MyDNS installation to version 1.1.0 or later.
CVE-2006-0351 affects MyDNS versions from 0.6 to 1.0.0.
CVE-2006-0351 has an unspecified impact that could lead to a denial-of-service condition.
There are no specific workarounds mentioned for CVE-2006-0351, so updating is the best approach.