First published: Tue Mar 07 2017(Updated: )
An out-of-bounds write flaw was found in the way Pidgin before 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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/pidgin | 2.13.0-2 2.14.1-1 2.14.12-1 | |
redhat/pidgin | <2.12.0 | 2.12.0 |
Pidgin | <2.12.0 | |
Debian Linux | =8.0 | |
Red Hat Enterprise Linux Desktop | =7.0 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Server | =7.4 | |
Red Hat Enterprise Linux Server | =7.4 | |
Red Hat Enterprise Linux Server | =7.5 | |
Red Hat Enterprise Linux Workstation | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-2640 has a high severity rating due to its potential to allow remote code execution or crash the application.
To fix CVE-2017-2640, upgrade Pidgin to versions 2.13.0, 2.14.1, or 2.14.12 or later.
Pidgin versions prior to 2.12.0 are affected by CVE-2017-2640.
CVE-2017-2640 presents risks such as crashing the Pidgin application and executing arbitrary code on a vulnerable system.
CVE-2017-2640 affects Pidgin on multiple operating systems including Debian and Red Hat platforms.