CVE-2013-0273: Medium severity pidgin vulnerability
Published Feb 16, 2013
·Updated
sametime.c in the Sametime protocol plugin in libpurple in Pidgin before 2.10.7 does not properly terminate long user IDs, which allows remote servers to cause a denial of service (application crash) via a crafted packet.
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-0273?
CVE-2013-0273 is classified as a denial-of-service vulnerability that can lead to application crashes.
2
How do I fix CVE-2013-0273?
To fix CVE-2013-0273, upgrade Pidgin to version 2.10.7 or later.
3
Which versions of Pidgin are affected by CVE-2013-0273?
CVE-2013-0273 affects Pidgin versions prior to 2.10.7, including several earlier versions.
4
What kind of attack does CVE-2013-0273 enable?
CVE-2013-0273 allows attackers to send specially crafted packets that can cause vulnerability exploitation leading to application crashes.
5
Is there a workaround for CVE-2013-0273?
There are no specific workarounds for CVE-2013-0273; updating to a patched version is strongly recommended.