CVE-2006-4611: Buffer overflow in the _tor_resolve function in dsocks.c in dsocks before 1.4 allows remote attackers to execu
CVE-2006-4611 is a high-severity flaw (CVSS 7.5) affecting dsocks. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Buffer overflow in the _tor_resolve function in dsocks.c in dsocks before 1.4 allows remote attackers to execute arbitrary code via unspecified vectors, possibly involving a long node name.
Why this priority
- High severity
- EPSS top 5%: very likely to be exploited
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| EPSS exploit chance | 8.0% (top 5%) |
| CISA exploited list | No |
| Published | 2006-09-07 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- Exploit-DB: DSocks 1.3 - 'Name' Buffer Overflow (PoC)
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-2006-4611?
dsocks: upgrade to newer than 1.3. Exact commands for each OS are on this page.
Is CVE-2006-4611 being exploited?
CVE-2006-4611 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-2006-4611 affect?
CVE-2006-4611 affects dsocks. Severity is high (CVSS 7.5). Buffer overflow in the _tor_resolve function in dsocks.c in dsocks before 1.4 allows remote attackers to execute arbitrary code via unspecified vectors, possibly involving a long node name.
How urgent is CVE-2006-4611?
Priority 55/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference