CVE-2010-3711: Input Validation

Published Oct 11, 2010
·
Updated

libpurple in Pidgin before 2.7.4 does not properly validate the return value of the purplebase64decode function, which allows remote authenticated users to cause a denial of service (NULL pointer dereference and application crash) via a crafted message, related to the plugins for MSN, MySpaceIM, XMPP, and Yahoo! and the NTLM authentication support.

Other sources

Pidgin did not sanitize output of Base64 decode operation prior its further processing. A remote attacker, valid Pidgin user, could use this flaw to cause:

a, NULL pointer dereference (pidgin daemon crash) by transfering of a specially-crafted buddy icon via the Yahoo protocol plugin

b, NULL pointer dereference (pidgin deamon crash) by providing a specially-crafted IP address value for peer-to-peer connection in the Yahoo protocol plugin

c, NULL pointer dereference (pidgin daemon crash) by providing a specially-crafted transfer header in the MSN protocol plugin

d, NULL pointer dereference (pidgin daemon crash) by providing a specially-crafted login challenge value in the MySpace protocol plugin

e, NULL pointer dereference (pidgin daemon crash) by providing a specially-crafted Digest-MD5 authentication challenge in the XMPP protocol plugin

Note: This crash can happen only when Cyrus SASL is not available or does not provide Digest-MD5 support

f, NULL pointer dereference (pidgin daemon crash) by providing a specially-crafted Type 2 message by authentication via the NTLM protocol

Acknowledgements:

Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Daniel Atallah as the original reporter.

Affected Software

34 affected components
Pidgin Pidgin=2.5.9
Pidgin Pidgin=2.5.8
Pidgin Pidgin<=2.7.3
Pidgin Pidgin=2.7.0
Pidgin Pidgin=2.1.0
Pidgin Pidgin=2.6.0
Pidgin Pidgin=2.5.2
Pidgin Pidgin=2.5.1
Pidgin Pidgin=2.5.6
Pidgin Pidgin=2.5.7
Pidgin Pidgin=2.0.1
Pidgin Pidgin=2.4.2
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.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.5.3
Pidgin Pidgin=2.6.1
Pidgin Pidgin=2.6.4
Pidgin Pidgin=2.7.2
Pidgin Pidgin=2.7.1

Event History

Oct 11, 2010
Data Sourced
02:38 PM
DescriptionSeverityAffected Software
Oct 27, 2010
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10: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-2010-3711?

CVE-2010-3711 has been classified as a denial-of-service vulnerability, which can result in application crashes.

2

How do I fix CVE-2010-3711?

To fix CVE-2010-3711, upgrade to Pidgin version 2.7.4 or later, which resolves the issue.

3

What versions of Pidgin are affected by CVE-2010-3711?

CVE-2010-3711 affects Pidgin versions prior to 2.7.4, including several earlier versions such as 2.5.0 to 2.7.3.

4

Can CVE-2010-3711 be exploited remotely?

Yes, CVE-2010-3711 can be exploited by remote authenticated users through crafted messages.

5

What are the risks associated with CVE-2010-3711?

The main risk associated with CVE-2010-3711 is a denial of service, which can disrupt user access to the application.

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