CVE-2013-0271 json
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) m…
published 2013-02-16 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-0297
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pidgin Debian 14, Debian 13, Debian 12 2.10.6-3
debian advisories DEBIAN-CVE-2013-0271
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-0271 updated cvss 3.3
pidgin: MXit protocol insufficient sanitization of saved image file names
-
Red Hat Enterprise Linux 5 pidgin Red Hat Enterprise Linux 6 finch, pidgin, libpurple, pidgin-perl, libpurple-tcl, libpurple-perlnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.12% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
References
-
lists.opensuse.org
/opensuse-security-announce/2013-03/msg00003.html
vendor-advisory
-
ubuntu.com
/usn/USN-1746-1
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-03/msg00006.html
vendor-advisory
-
pidgin.im
/news/security/?id=65
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A18386
vdb-entry, signature
- hg.pidgin.im /pidgin/main/rev/a8aef1d340f2
Sources
- CVE List CVE-2013-0271
- NVD CVE-2013-0271
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.