9.8
CVSSv3

CVE-2017-2640

Published: 27/07/2018 Updated: 09/10/2019
CVSS v2 Base Score: 7.5 | Impact Score: 6.4 | Exploitability Score: 10
CVSS v3 Base Score: 9.8 | Impact Score: 5.9 | Exploitability Score: 3.9
VMScore: 668
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P

Vulnerability Summary

An out-of-bounds write flaw was found in the way Pidgin prior to 2.12.0 processed XML content. A malicious remote server could potentially use this flaw to crash Pidgin or execute arbitrary code in the context of the pidgin process.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

pidgin pidgin

redhat enterprise linux server 7.0

redhat enterprise linux server eus 7.5

redhat enterprise linux server aus 7.4

redhat enterprise linux desktop 7.0

redhat enterprise linux server eus 7.4

redhat enterprise linux workstation 7.0

debian debian linux 8.0

Vendor Advisories

Synopsis Moderate: pidgin security, bug fix, and enhancement update Type/Severity Security Advisory: Moderate Topic An update for pidgin is now available for Red Hat Enterprise Linux 7Red Hat Product Security has rated this update as having a security impact of Moderate A Common Vulnerability Scoring Syst ...
Debian Bug report logs - #859159 pidgin: CVE-2017-2640 Package: pidgin; Maintainer for pidgin is Ari Pollak <ari@debianorg>; Source for pidgin is src:pidgin (PTS, buildd, popcon) Reported by: Salvatore Bonaccorso <carnil@debianorg> Date: Fri, 31 Mar 2017 04:57:01 UTC Severity: grave Tags: security Found in versio ...
Pidgin could be made to crash or run programs if it received specially crafted network traffic ...
It was discovered a vulnerability in Pidgin, a multi-protocol instant messaging client A server controlled by an attacker can send an invalid XML that can trigger an out-of-bound memory access This might lead to a crash or, in some extreme cases, to remote code execution in the client-side For the stable distribution (jessie), this problem has b ...
An out-of-bounds write has been found in libpurple < 2120 in the purple_markup_unescape_entity function This issue can be triggered by a malicious server sending invalid XML entities separated by whitespace, eg "ஸ" to the client ...