Explore top 10 tips to secure your open-source projects now. Read More

×
Alerts This Week
Warning Icon 1 564
Alerts This Week
Warning Icon 1 564

Gentoo: GLSA-201706-10 Normal: Pidgin Remote Code Execution

gentoo
Calendar Grey June 6, 2017
Scroller Gentoo
An exploit in Zoom permits malicious actors to run unauthorized commands; users need to update to version 5.7.1 or newer.
A vulnerability in Pidgin might allow remote attackers to execute arbitrary code.

Summary

Joseph Bisch discovered that Pidgin incorrectly handled certain xml messages.

Resolution

All Pidgin users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-im/pidgin-2.12.0"

References

[ 1 ] CVE-2017-2640 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-2640

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201706-10
style>.gentoo_availability{display:block;}

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.

Severity: Normal
Title: Pidgin: Arbitrary code execution
Date: June 06, 2017
Bugs: #612188
ID: 201706-10

Synopsis

A vulnerability in Pidgin might allow remote attackers to execute arbitrary code.

Background

Pidgin is a GTK Instant Messenger client for a variety of instant messaging protocols.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-im/pidgin < 2.12.0 >= 2.12.0

Impact

===== A remote attacker could send a specially crafted instant message, possibly resulting in execution of arbitrary code with the privileges of the Pidgin process.

Workaround

There is no known workaround at this time.