Gentoo: GLSA-201006-07: SILC: Multiple vulnerabilities
Summary
Multiple vulnerabilities were discovered in SILC Toolkit and SILC Client. For further information please consult the CVE entries referenced below.
Resolution
All SILC Toolkit users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-im/silc-toolkit-1.1.10"
All SILC Client users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-im/silc-client-1.1.8"
References
[ 1 ] CVE-2008-7159 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-7159 [ 2 ] CVE-2008-7160 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-7160 [ 3 ] CVE-2009-3051 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3051 [ 4 ] CVE-2009-3163 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3163
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201006-07
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 were discovered in SILC Toolkit and SILC Client, the worst of which allowing for execution of arbitrary code.
Background
SILC (Secure Internet Live Conferencing protocol) Toolkit is a software development kit for use in clients, and SILC Client is an IRSSI-based text client.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-im/silc-toolkit < 1.1.10 >= 1.1.10 2 net-im/silc-client < 1.1.8 >= 1.1.8 ------------------------------------------------------------------- 2 affected packages on all of their supported architectures. -------------------------------------------------------------------
Impact
===== A remote attacker could overwrite stack locations and possibly execute arbitrary code via a crafted OID value, Content-Length header or format string specifiers in a nickname field or channel name.
Workaround
There is no known workaround at this time.