CVE-2013-0271: Medium severity pidgin vulnerability
Published Feb 16, 2013
·Updated
The MXit protocol plugin in libpurple in Pidgin before 2.10.7 might allow remote attackers to create or overwrite files via a crafted (1) mxit or (2) mxit/imagestrips pathname.
Affected Software
51 affected components
Pidgin Pidgin<=2.10.6
Pidgin Pidgin=2.0.0
Pidgin Pidgin=2.0.1
Pidgin Pidgin=2.0.2
Pidgin Pidgin=2.1.0
Pidgin Pidgin=2.1.1
Pidgin Pidgin=2.2.0
Pidgin Pidgin=2.2.1
Pidgin Pidgin=2.2.2
Pidgin Pidgin=2.3.0
Pidgin Pidgin=2.3.1
Pidgin Pidgin=2.4.0
Pidgin Pidgin=2.4.1
Pidgin Pidgin=2.4.2
Pidgin Pidgin=2.4.3
Pidgin Pidgin=2.5.0
Pidgin Pidgin=2.5.1
Pidgin Pidgin=2.5.2
Pidgin Pidgin=2.5.3
Pidgin Pidgin=2.5.4
Pidgin Pidgin=2.5.5
Pidgin Pidgin=2.5.6
Pidgin Pidgin=2.5.7
Pidgin Pidgin=2.5.8
Pidgin Pidgin=2.5.9
Pidgin Pidgin=2.6.0
Pidgin Pidgin=2.6.1
Pidgin Pidgin=2.6.2
Pidgin Pidgin=2.6.4
Pidgin Pidgin=2.6.5
Pidgin Pidgin=2.6.6
Pidgin Pidgin=2.7.0
Pidgin Pidgin=2.7.1
Pidgin Pidgin=2.7.2
Pidgin Pidgin=2.7.3
Pidgin Pidgin=2.7.4
Pidgin Pidgin=2.7.5
Pidgin Pidgin=2.7.6
Pidgin Pidgin=2.7.7
Pidgin Pidgin=2.7.8
Pidgin Pidgin=2.7.9
Pidgin Pidgin=2.7.10
Pidgin Pidgin=2.7.11
Pidgin Pidgin=2.8.0
Pidgin Pidgin=2.9.0
Pidgin Pidgin=2.10.0
Pidgin Pidgin=2.10.1
Pidgin Pidgin=2.10.2
Pidgin Pidgin=2.10.3
Pidgin Pidgin=2.10.4
Pidgin Pidgin=2.10.5
Event History
Feb 16, 2013
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-0271?
CVE-2013-0271 is considered a medium severity vulnerability due to the potential for unauthorized file creation or overwriting.
2
How do I fix CVE-2013-0271?
You can fix CVE-2013-0271 by upgrading to Pidgin version 2.10.7 or later.
3
What versions of Pidgin are affected by CVE-2013-0271?
CVE-2013-0271 affects all Pidgin versions prior to 2.10.7, including versions from 2.0.0 to 2.10.6.
4
What type of vulnerability is CVE-2013-0271?
CVE-2013-0271 is a file manipulation vulnerability that allows remote attackers to create or overwrite files.
5
Is there a workaround for CVE-2013-0271?
There is no documented workaround for CVE-2013-0271; upgrading to the secure version is recommended.