Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1154910 - (CVE-2014-3696) CVE-2014-3696 pidgin: denial of service parsing Groupwise server message
CVE-2014-3696 pidgin: denial of service parsing Groupwise server message
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20141022,repor...
: Reopened, Security
Depends On: 1155838 1340770 1403136 1446519
Blocks: 1154913 1415638
  Show dependency treegraph
 
Reported: 2014-10-20 23:21 EDT by Murray McAllister
Modified: 2018-09-27 07:30 EDT (History)
7 users (show)

See Also:
Fixed In Version: pidgin 2.10.10
Doc Type: Bug Fix
Doc Text:
A denial of service flaw was found in the way Pidgin parsed Groupwise server messages. A malicious remote server or a man-in-the-middle attacker could potentially use this flaw to cause Pidgin to consume an excessive amount of memory, possibly leading to a crash, by sending a specially crafted message.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-12-16 14:30:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch from upstream (4.51 KB, patch)
2014-10-20 23:22 EDT, Murray McAllister
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1854 normal SHIPPED_LIVE Moderate: pidgin security, bug fix, and enhancement update 2017-08-01 14:23:14 EDT

  None (edit)
Description Murray McAllister 2014-10-20 23:21:44 EDT
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)
Comment 1 Murray McAllister 2014-10-20 23:22:22 EDT
Created attachment 948788 [details]
patch from upstream
Comment 3 Murray McAllister 2014-10-22 21:20:21 EDT
Public now:

http://www.pidgin.im/news/security/?id=88
Comment 4 Murray McAllister 2014-10-22 21:27:12 EDT
Created pidgin tracking bugs for this issue:

Affects: fedora-all [bug 1155838]
Comment 5 Fedora Update System 2014-11-10 01:31:38 EST
pidgin-2.10.10-2.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 6 Fedora Update System 2014-11-10 01:47:39 EST
pidgin-2.10.10-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 7 Siddharth Sharma 2014-11-21 06:46:27 EST
Analysis:

In the function handle_receive_message(), variable named "size" is defined as "guint32 size= 0;",Values of this guint32 can range from 0 to G_MAXUINT32 (= 4,294,967,295). Then the stream is read from the connection and passed into "size" by the following code

rc = nm_read_uint32(conn, &size);

after that size validation happens , but here as it is compared with MAX_UINT32 because of which size variable can contain really large value.

if (size == MAX_UINT32)	return NMERR_PROTOCOL;

after that the memory allocation happens which  also depends on the variable "size"

  g_new0(char, size +1);
  
which could lead to large amount of memory allocation further leading to DOS or crash while parsing server message.As this needs client to connect to malicious server, this requires some social engineering to convince user to connect to malicious server. Man-in-the-middle attacker could also use this attack vector which would cause pidgin to allocate an excessive amount of memory slowing down victims system, possibly leading to a crash of application.
Comment 14 errata-xmlrpc 2017-08-01 16:20:56 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2017:1854 https://access.redhat.com/errata/RHSA-2017:1854

Note You need to log in before you can comment on or make changes to this bug.