CVE-2006-0351: Medium severity Don Moore Mydns vulnerability
Published Jan 21, 2006
·Updated
Unspecified "critical denial-of-service vulnerability" in MyDNS before 1.1.0 has unknown impact and attack vectors.
Affected Software
26 affected components
Don Moore Mydns=0.6
Don Moore Mydns=0.7
Don Moore Mydns=0.7.1
Don Moore Mydns=0.8
Don Moore Mydns=0.8.1
Don Moore Mydns=0.8.2
Don Moore Mydns=0.8.3
Don Moore Mydns=0.9.0
Don Moore Mydns=0.9.1
Don Moore Mydns=0.9.2
Don Moore Mydns=0.9.3
Don Moore Mydns=0.9.5
Don Moore Mydns=0.9.6
Don Moore Mydns=0.9.7
Don Moore Mydns=0.9.8
Don Moore Mydns=0.9.9
Don Moore Mydns=0.9.10
Don Moore Mydns=0.9.12
Don Moore Mydns=0.9.13
Don Moore Mydns=0.10.0
Don Moore Mydns=0.10.1
Don Moore Mydns=0.10.2
Don Moore Mydns=0.10.3
Don Moore Mydns=0.10.4
Don Moore Mydns=0.11.0
Don Moore Mydns=1.0.0
Remediation
Patch Available
Patch Available
Event History
Jan 21, 2006
CVE Published
01:03 AM
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2006-0351?
CVE-2006-0351 is classified as a critical denial-of-service vulnerability.
2
How do I fix CVE-2006-0351?
To resolve CVE-2006-0351, upgrade your MyDNS installation to version 1.1.0 or later.
3
What versions are affected by CVE-2006-0351?
CVE-2006-0351 affects MyDNS versions from 0.6 to 1.0.0.
4
What impact does CVE-2006-0351 have on MyDNS?
CVE-2006-0351 has an unspecified impact that could lead to a denial-of-service condition.
5
Are there any workarounds for CVE-2006-0351 until I can update?
There are no specific workarounds mentioned for CVE-2006-0351, so updating is the best approach.