First published: Tue Oct 21 2014(Updated: )
It flaw was reported in the way Groupwise server messages were parsed. A malicious server or man-in-the-middle attacker could send a specially-crafted message that could cause Pidgin to attempt to allocate an excessive amount of memory, possibly leading to a crash. Acknowledgements: Name: the Pidgin project Upstream: Yves Younan (Cisco Talos), Richard Johnson (Cisco Talos)
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/pidgin | <2.10.10 | 2.10.10 |
Pidgin | <=2.10.9 | |
Pidgin | =2.10.0 | |
Pidgin | =2.10.1 | |
Pidgin | =2.10.2 | |
Pidgin | =2.10.3 | |
Pidgin | =2.10.4 | |
Pidgin | =2.10.5 | |
Pidgin | =2.10.6 | |
Pidgin | =2.10.7 | |
Pidgin | =2.10.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-3696 is considered a medium severity vulnerability due to its potential to crash the Pidgin application.
To fix CVE-2014-3696, upgrade Pidgin to version 2.10.10 or later.
CVE-2014-3696 affects Pidgin versions up to 2.10.9.
CVE-2014-3696 could be exploited by a malicious server or a man-in-the-middle attacker.
If not addressed, CVE-2014-3696 can cause Pidgin to allocate excessive memory and potentially crash.