Pidgin 2.x null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.6$0-$5k0.00

Summaryinfo

A vulnerability was found in Pidgin 2.x. It has been declared as problematic. This affects an unknown part. Executing a manipulation can lead to null pointer dereference. This vulnerability is tracked as CVE-2011-2943. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Pidgin 2.x (Messaging Software). This vulnerability affects some unknown processing. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:

The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

The weakness was disclosed 08/22/2011 by James Burton (Website). The advisory is available at pidgin.im. This vulnerability was named CVE-2011-2943 since 07/27/2011. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.

The vulnerability scanner Nessus provides a plugin with the ID 55928 (Pidgin < 2.10.0 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 120535 (Solaris Multiple Vulnerabilities in Pidgin).

Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at pidgin.im. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (69340), Tenable (55928), SecurityFocus (BID 49268†), Secunia (SA45663†) and SecurityTracker (ID 1025961†). The entries VDB-55936, VDB-56831, VDB-61515 and VDB-60433 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.6

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 55928
Nessus Name: Pidgin < 2.10.0 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 831451
OpenVAS Name: Mandriva Update for pidgin MDVSA-2011:132 (pidgin)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Patch: pidgin.im

Timelineinfo

07/27/2011 🔍
08/20/2011 +24 days 🔍
08/20/2011 +0 days 🔍
08/20/2011 +0 days 🔍
08/22/2011 +2 days 🔍
08/22/2011 +0 days 🔍
08/22/2011 +0 days 🔍
08/22/2011 +0 days 🔍
08/29/2011 +7 days 🔍
08/30/2011 +1 days 🔍
09/16/2011 +17 days 🔍
03/19/2021 +3472 days 🔍

Sourcesinfo

Advisory: pidgin.im
Researcher: James Burton
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2011-2943 (🔍)
GCVE (CVE): GCVE-0-2011-2943
GCVE (VulDB): GCVE-100-4402

OVAL: 🔍

X-Force: 69340
SecurityFocus: 49268 - Pidgin Denial of Service and Security Bypass Vulnerabilities
Secunia: 45663 - Pidgin Denial of Service Weaknesses and "file://" Security Issue, Moderately Critical
SecurityTracker: 1025961 - Pidgin Bugs Let Remote Users Deny Service and Potentially Execute Arbitrary Code
Vulnerability Center: 32875 - libpurple 2.8.0-2.9.0 in Pidgin prior to 2.10.0 Remote DoS Vulnerability via a Crafted Nickname, Medium

See also: 🔍

Entryinfo

Created: 09/16/2011 02:00
Updated: 03/19/2021 14:25
Changes: 09/16/2011 02:00 (75), 03/30/2017 10:25 (16), 03/19/2021 14:25 (3)
Complete: 🔍
Cache ID: 216:412:103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!