Red Hat Bugzilla – Bug 894092
CVE-2013-0722 ettercap: stack-based buffer overflow when parsing hosts list
Last modified: 2016-03-04 05:47:12 EST
A stack-based buffer overflow was reported , in Ettercap <= 0.7.5.1. A boundary error within the scan_load_hosts() function (in src/ec_scan.c), when parsing entries from a hosts list, could be exploited to cause a stack-based buffer overflow via an overly long entry. In order to exploit this, a user must be tricked into loading a malicious host file.
This has not yet been corrected upstream, but a proposed patch is available .
The initial report  indicates that this was given the name CVE-2012-0722.
Created ettercap tracking bugs for this issue
Affects: fedora-all [bug 894094]
Affects: epel-all [bug 894096]
This was meant to be CVE-2013-0722, not a 2012 CVE.
This has been fixed upstream, you can cherry pick the patch or wait for the next tag.
The new version will bring up many bug fix including this one
0.7.5.2 fixes this issue.
When is it going to be released?
(In reply to comment #5)
> When is it going to be released?
Ah, I see. It's not on the website. :)
Please don't update to 0.7.5.2 unless you patch include/ec_version.h file!
Is still in the old version, I think we will release 0.7.5.3 soon
Ok, my build failed for some reason anyway, please let me know as soon as 0.7.5.3 is out.
(In reply to comment #9)
> Ok, my build failed for some reason anyway, please let me know as soon as
> 0.7.5.3 is out.
It doesn't fail here(on gentoo), what's your problem?
I was fine locally and in mock, but failed in koji in rawhide. Investigating. Might have been temporary rawhide brokenness.
I wasn't requiring groff for the build, I fixed it, it's fine now.
The problem for 0.7.5.2 is only cosmetic, ec_include.h defines the version as 0.7.5.1, so just the menu title is not updated, not a really bug :))
wich kind of error do you receive?
Nothing, when groff is present.
I don't know what groff means... :-) BTW ettercap 0.7.5.3 is out, just two minor.fix about versioning and a fedora bug fixed upstream.
This has been fixed now via: