Pidgin 2.10.7 Yahoo! Protocol Plugin Non-UTF-8 String input validation

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.
6.5$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Pidgin 2.10.7. Affected is an unknown function of the component Yahoo! Protocol Plugin. This manipulation as part of Non-UTF-8 String causes input validation. This vulnerability is handled as CVE-2012-6152. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Pidgin 2.10.7 (Messaging Software). It has been declared as critical. Affected by this vulnerability is an unknown code of the component Yahoo! Protocol Plugin. The manipulation as part of a Non-UTF-8 String leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect availability. The summary by CVE is:

The Yahoo! protocol plugin in libpurple in Pidgin before 2.10.8 does not properly validate UTF-8 data, which allows remote attackers to cause a denial of service (application crash) via crafted byte sequences.

The weakness was released 01/28/2014 by Thijs Alkemade and Robert Vehse with Coverity static analysis as Yahoo! remote crash from incorrect character encoding as confirmed advisory (Website). The advisory is shared at pidgin.im. This vulnerability is known as CVE-2012-6152 since 12/06/2012. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 72364 (RHEL 5 / 6 : pidgin (RHSA-2014:0139)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 166900 (SUSE Enterprise Linux Security Update for finch (SUSE-SU-2014:0702-1)).

Upgrading to version 2.10.8 eliminates this vulnerability. The upgrade is hosted for download at hg.pidgin.im. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (91299), Tenable (72364), SecurityFocus (BID 57951†), OSVDB (102629†) and Vulnerability Center (SBV-43176†). Additional details are provided at linux-magazin.de. Entries connected to this vulnerability are available at VDB-7732, VDB-7733, VDB-12106 and VDB-12107. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 6.5

VulDB Base Score: 7.5
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 72364
Nessus Name: RHEL 5 / 6 : pidgin (RHSA-2014:0139)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

OpenVAS ID: 881871
OpenVAS Name: CentOS Update for finch CESA-2014:0139 centos5
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Pidgin 2.10.8

Timelineinfo

12/06/2012 🔍
02/13/2013 +69 days 🔍
01/28/2014 +349 days 🔍
01/28/2014 +0 days 🔍
01/31/2014 +3 days 🔍
02/04/2014 +4 days 🔍
02/06/2014 +2 days 🔍
02/06/2014 +0 days 🔍
02/06/2014 +0 days 🔍
06/08/2021 +2679 days 🔍

Sourcesinfo

Advisory: Yahoo! remote crash from incorrect character encoding
Researcher: Thijs Alkemade, Robert Vehse
Organization: Coverity static analysis
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2012-6152 (🔍)
GCVE (CVE): GCVE-0-2012-6152
GCVE (VulDB): GCVE-100-12121

OVAL: 🔍

X-Force: 91299 - Pidgin Yahoo! protocol plugin denial of service, Medium Risk
SecurityFocus: 57951 - Pidgin 'libpurple' CVE-2013-0272 HTTP Header Stack Buffer Overflow Vulnerability
OSVDB: 102629
Vulnerability Center: 43176 - Pidgin Prior to 2.10.8 Remote DoS Vulnerability due to an Error in the Yahoo! Protocol Plugin - CVE-2012-6152, Medium

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 01/31/2014 10:18
Updated: 06/08/2021 20:54
Changes: 01/31/2014 10:18 (83), 05/20/2017 10:29 (5), 06/08/2021 20:54 (3)
Complete: 🔍
Cache ID: 216:C67:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!