CVE-2006-4611
Buffer overflow in the _tor_resolve function in dsocks.c in dsocks before 1.4 allows remote...
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.
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2006-4611- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2006-4611- Updated
- 2026-11-02
EUVDEUVD-2006-4599 No score
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.
- Record
EUVD-2006-4599- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-583w-6h2g-rxp3 No score
Buffer overflow in the _tor_resolve function in dsocks.c in dsocks before 1.4 allows remote...
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.
- Record
GHSA-583w-6h2g-rxp3- Updated
- 2026-11-02
Affected products
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | DSocks 1.3 - 'Name' Buffer Overflow (PoC) | 2006-09-05 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2006-4611 is a high vulnerability (CVSS 7.5) in Dsocks, published September 7, 2006. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 7.99%, the 94th percentile. No source names a fixed version.