CVE-2006-2646: Buffer Overflow
First published: Tue May 30 2006(Updated: )
Buffer overflow in Alt-N MDaemon, possibly 9.0.1 and earlier, allows remote attackers to execute arbitrary code via a long A0001 argument that begins with a '"' (double quote).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MDaemon | =2.8 | |
| MDaemon | =2.8.5.0 | |
| MDaemon | =3.0.3 | |
| MDaemon | =3.0.4 | |
| MDaemon | =3.1.1 | |
| MDaemon | =3.1.2 | |
| MDaemon | =3.1_beta | |
| MDaemon | =3.5.0 | |
| MDaemon | =3.5.1 | |
| MDaemon | =3.5.4 | |
| MDaemon | =3.5.4 | |
| MDaemon | =3.5.4 | |
| MDaemon | =3.5.6 | |
| MDaemon | =5.0 | |
| MDaemon | =5.0 | |
| MDaemon | =5.0.1 | |
| MDaemon | =5.0.2 | |
| MDaemon | =5.0.3 | |
| MDaemon | =5.0.4 | |
| MDaemon | =5.0.5 | |
| MDaemon | =5.0.6 | |
| MDaemon | =5.0.7 | |
| MDaemon | =6.0 | |
| MDaemon | =6.0.5 | |
| MDaemon | =6.0.6 | |
| MDaemon | =6.0.7 | |
| MDaemon | =6.5.0 | |
| MDaemon | =6.5.1 | |
| MDaemon | =6.5.2 | |
| MDaemon | =6.7.5 | |
| MDaemon | =6.7.9 | |
| MDaemon | =6.8.0 | |
| MDaemon | =6.8.1 | |
| MDaemon | =6.8.2 | |
| MDaemon | =6.8.3 | |
| MDaemon | =6.8.4 | |
| MDaemon | =6.8.5 | |
| MDaemon | =7.2 | |
| MDaemon | =8.1.1 | |
| MDaemon | =8.1.3 | |
| MDaemon | =8.1.4 | |
| MDaemon | =9.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2006-2646?
CVE-2006-2646 is classified with high severity due to its potential to allow remote code execution.
How do I fix CVE-2006-2646?
To fix CVE-2006-2646, you should upgrade to a patched version of Alt-N MDaemon that addresses the buffer overflow vulnerability.
What versions of Alt-N MDaemon are affected by CVE-2006-2646?
CVE-2006-2646 affects multiple versions of Alt-N MDaemon including 9.0.1 and earlier, specifically versions from 2.8 up to 9.0.1.
Can CVE-2006-2646 be exploited remotely?
Yes, CVE-2006-2646 can be exploited remotely, allowing attackers to execute arbitrary code.
Is there a workaround for CVE-2006-2646?
There are no effective workarounds for CVE-2006-2646; updating to a secure version is the recommended solution.
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/tags
- agent/description
- agent/softwarecombine
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/alt-n
- product/mdaemon
- canonical/alt-n mdaemon
- canonical/mdaemon
- version/mdaemon/2.8
- version/mdaemon/2.8.5.0
- version/mdaemon/3.0.3
- version/mdaemon/3.0.4
- version/mdaemon/3.1.1
- version/mdaemon/3.1.2
- version/mdaemon/3.1_beta
- version/mdaemon/3.5.0
- version/mdaemon/3.5.1
- version/mdaemon/3.5.4
- version/mdaemon/3.5.6
- version/mdaemon/5.0
- version/mdaemon/5.0.1
- version/mdaemon/5.0.2
- version/mdaemon/5.0.3
- version/mdaemon/5.0.4
- version/mdaemon/5.0.5
- version/mdaemon/5.0.6
- version/mdaemon/5.0.7
- version/mdaemon/6.0
- version/mdaemon/6.0.5
- version/mdaemon/6.0.6
- version/mdaemon/6.0.7
- version/mdaemon/6.5.0
- version/mdaemon/6.5.1
- version/mdaemon/6.5.2
- version/mdaemon/6.7.5
- version/mdaemon/6.7.9
- version/mdaemon/6.8.0
- version/mdaemon/6.8.1
- version/mdaemon/6.8.2
- version/mdaemon/6.8.3
- version/mdaemon/6.8.4
- version/mdaemon/6.8.5
- version/mdaemon/7.2
- version/mdaemon/8.1.1
- version/mdaemon/8.1.3
- version/mdaemon/8.1.4
- version/mdaemon/9.0.1