{"id":"CVE-2006-4611","url":"https://www.cyber-defence.io/tools/cve/CVE-2006-4611","generatedAt":"2026-10-27T18:48:25.674Z","title":"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.","description":"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.","published":"2006-09-07T00:04:00.000Z","lastModified":"2026-06-16T22:29:27.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"2.0","score":7.5,"severity":"HIGH","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P"},"cwe":[],"affected":["dsocks/dsocks"],"epss":{"score":0.07985,"percentile":0.94718,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":1,"verified":true,"firstPublished":"2006-09-05","source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[{"edbId":28491,"kind":"exploit","title":"DSocks 1.3 - 'Name' Buffer Overflow (PoC)","url":"https://www.exploit-db.com/exploits/28491","sourceUrl":"https://gitlab.com/exploit-database/exploitdb/-/blob/main/exploits/multiple/dos/28491.txt","file":"exploits/multiple/dos/28491.txt","published":"2006-09-05","added":"2006-09-05","updated":"2013-09-23","author":"Michael Adams","type":"dos","platform":"multiple","port":null,"verified":true,"codes":["CVE-2006-4611","OSVDB-28621"],"tags":null,"aliases":null,"applicationUrl":null,"screenshotUrl":null,"referenceUrl":"https://www.securityfocus.com/bid/19852/info"}]},"verdict":{"level":"urgent","text":"A public exploit is published in Exploit-DB (verified) and the impact is high, while EPSS rates exploitation at 8.0%. Anyone can run this; patch or mitigate before the next change window and check exposed instances for signs of use."},"changes":[],"references":[{"url":"http://lists.grok.org.uk/pipermail/full-disclosure/2006-September/049258.html","source":"cve@mitre.org"},{"url":"http://secunia.com/advisories/21771","tags":["Vendor Advisory"],"source":"cve@mitre.org"},{"url":"http://securityreason.com/securityalert/1493","source":"cve@mitre.org"},{"url":"http://www.monkey.org/~dugsong/dsocks/","tags":["Patch"],"source":"cve@mitre.org"},{"url":"http://www.securityfocus.com/archive/1/445200/100/0/threaded","source":"cve@mitre.org"},{"url":"http://www.securityfocus.com/bid/19852","tags":["Exploit"],"source":"cve@mitre.org"},{"url":"http://www.vupen.com/english/advisories/2006/3526","source":"cve@mitre.org"},{"url":"https://exchange.xforce.ibmcloud.com/vulnerabilities/28762","source":"cve@mitre.org"},{"url":"https://www.exploit-db.com/exploits/2303","source":"cve@mitre.org"},{"url":"http://lists.grok.org.uk/pipermail/full-disclosure/2006-September/049258.html","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://secunia.com/advisories/21771","tags":["Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://securityreason.com/securityalert/1493","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://www.monkey.org/~dugsong/dsocks/","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://www.securityfocus.com/archive/1/445200/100/0/threaded","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://www.securityfocus.com/bid/19852","tags":["Exploit"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://www.vupen.com/english/advisories/2006/3526","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://exchange.xforce.ibmcloud.com/vulnerabilities/28762","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://www.exploit-db.com/exploits/2303","source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2006-4611","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}