CVE-2011-3184: Medium severity pidgin vulnerability

Published Aug 22, 2011
·
Updated

A flaw was found in the handling of HTTP 100 responses in the MSN protocol plugin. It can cause the application to attempt to access memory that it does not have access to. This only affects users who have turned on the HTTP connection method for their accounts (it's off by default). This might only be triggerable by a malicious server and not a malicious peer. Remote code execution is not possible.

Reference: http://pidgin.im/news/security/?id=54

Other sources

The msnhttpconnparsedata function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

MITRE

Affected Software

44 affected components
Pidgin Pidgin=2.5.9
Pidgin Pidgin=2.5.8
Pidgin Pidgin=2.7.9
Pidgin Pidgin=2.7.5
Pidgin Pidgin=2.7.0
Pidgin Pidgin=2.1.0
Pidgin Pidgin=2.7.4
Pidgin Pidgin=2.6.0
Pidgin Pidgin=2.5.2
Pidgin Pidgin=2.5.1
Pidgin Pidgin=2.7.6
Pidgin Pidgin=2.7.11
Pidgin Pidgin=2.5.6
Pidgin Pidgin=2.7.10
Pidgin Pidgin=2.5.7
Pidgin Pidgin=2.0.1
Pidgin Pidgin=2.4.2
Pidgin Pidgin=2.7.3
Pidgin Pidgin=2.5.4
Pidgin Pidgin=2.5.5
Pidgin Pidgin=2.6.5
Pidgin Pidgin=2.2.2
Pidgin Pidgin=2.1.1
Pidgin Pidgin=2.3.1
Pidgin Pidgin=2.4.3
Pidgin Pidgin=2.6.6
Pidgin Pidgin=2.8.0
Pidgin Pidgin=2.0.0
Pidgin Pidgin=2.0.2
Pidgin Pidgin=2.3.0
Pidgin Pidgin=2.4.1
Pidgin Pidgin=2.4.0
Pidgin Pidgin=2.6.2
Pidgin Pidgin=2.5.0
Pidgin Pidgin=2.2.0
Pidgin Pidgin=2.2.1
Pidgin Pidgin=2.7.8
Pidgin Pidgin<=2.9.0
Pidgin Pidgin=2.7.7
Pidgin Pidgin=2.5.3
Pidgin Pidgin=2.6.1
Pidgin Pidgin=2.6.4
Pidgin Pidgin=2.7.2
Pidgin Pidgin=2.7.1

Event History

Aug 22, 2011
Data Sourced
10:36 AM
DescriptionSeverityAffected Software
Aug 29, 2011
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-3184?

CVE-2011-3184 has a medium severity level due to its potential to allow unauthorized memory access.

2

How do I fix CVE-2011-3184?

To fix CVE-2011-3184, update Pidgin to a version later than 2.8.0 where the vulnerability is patched.

3

Which software versions are affected by CVE-2011-3184?

CVE-2011-3184 affects Pidgin versions from 2.0.0 to 2.8.0.

4

What type of vulnerability is CVE-2011-3184?

CVE-2011-3184 is a memory access vulnerability resulting from improper handling of HTTP 100 responses.

5

Who is at risk for CVE-2011-3184?

Users of Pidgin who have enabled the HTTP connection method are at risk for CVE-2011-3184.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203