Gentoo: GLSA-201405-12: Ettercap: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in Ettercap:
* Ettercap does not handle temporary files securely (CVE-2010-3843).
* A format string flaw in Ettercap could cause a buffer overflow
(CVE-2010-3844).
* A stack-based buffer overflow exists in Ettercap (CVE-2013-0722).
Resolution
All Ettercap users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-analyzer/ettercap-0.7.5.2"
References
[ 1 ] CVE-2010-3843 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3843 [ 2 ] CVE-2010-3844 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3844 [ 3 ] CVE-2013-0722 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0722
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201405-12
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
![Dist Gentoo](/images/distros/dist-gentoo.png)
Synopsis
Multiple vulnerabilities have been found in Ettercap, the worst of which may allow execution of arbitrary code.
Background
Ettercap is a suite of tools for content filtering, sniffing and man in the middle attacks on a LAN.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-analyzer/ettercap < 0.7.5.2 >= 0.7.5.2
Impact
=====
A remote attacker could entice a user to load a specially crafted
configuration file using Ettercap, possibly resulting in execution of
arbitrary code with the privileges of the process or a Denial of
Service condition.
A local attacker could perform symlink attacks to overwrite arbitrary
files with the privileges of the user running the application.
Workaround
There is no known workaround at this time.