The msn_oim_report_to_user function in oim.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.2 allows remote servers to cause
The msn_oim_report_to_user function in oim.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.2 allows remote servers to cause a denial of service (application crash) via an OIM message that lacks UTF-8 encoding.
- Published
- Mar 15, 2012
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-399
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| pidgin | pidgin | cpe:2.3:a:pidgin:pidgin |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pidgin pidginup to 2.10.1 inclusive
- pidgin pidgin2.0.0
- pidgin pidgin2.0.1
- pidgin pidgin2.0.2
- pidgin pidgin2.1.0
- pidgin pidgin2.1.1
- pidgin pidgin2.10.0
- pidgin pidgin2.2.0
- pidgin pidgin2.2.1
- pidgin pidgin2.2.2
- pidgin pidgin2.3.0
- pidgin pidgin2.3.1
- pidgin pidgin2.4.0
- pidgin pidgin2.4.1
- pidgin pidgin2.4.2
- pidgin pidgin2.4.3
- pidgin pidgin2.5.0
- pidgin pidgin2.5.1
- pidgin pidgin2.5.2
- pidgin pidgin2.5.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pidgin | before 2.10.2-1 | 2.10.2-1 |
| Red Hat:enterprise_linux:5::client | finch | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client | libpurple | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client | libpurple-perl | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client | libpurple-tcl | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client | pidgin | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client | pidgin-debuginfo | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client | pidgin-perl | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client_workstation | finch-devel | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client_workstation | libpurple-devel | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:5::client_workstation | pidgin-devel | before 0:2.6.6-11.el5.4 | 0:2.6.6-11.el5.4 |
| Red Hat:enterprise_linux:6::client | finch | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | finch-devel | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | libpurple | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | libpurple-devel | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | libpurple-perl | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | libpurple-tcl | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | pidgin | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | pidgin-debuginfo | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | pidgin-devel | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | pidgin-docs | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
| Red Hat:enterprise_linux:6::client | pidgin-perl | before 0:2.7.9-5.el6.2 | 0:2.7.9-5.el6.2 |
Same product
pidgin: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-2694The msn_slplink_process_msg function in libpurple/protocols/msn/slplink.c in libpurple, as used in Pidgin (formerly Gaim) before 2.5.9 and A46Plan
- CVE-2013-6490The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative Content-Lengt44Plan
- CVE-2017-2640An out-of-bounds write flaw was found in the way Pidgin before 2.12.0 processed XML content.41Plan
- CVE-2009-1376Multiple integer overflows in the msn_slplink_process_msg functions in the MSN protocol handler in (1) libpurple/protocols/msn/slplink.c and41Plan
- CVE-2016-1000030Pidgin version <2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutl40Plan
- CVE-2013-6486gtkutils.c in Pidgin before 2.10.8 on Windows allows user-assisted remote attackers to execute arbitrary programs via a message containing a38Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Debian:pidgin | 2.10.2-1 · Debian:12 | Package registry (OSV) |
| Red Hat:finch | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| Red Hat:finch-devel | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| Red Hat:libpurple | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| Red Hat:libpurple-devel | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| Red Hat:libpurple-perl | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| Red Hat:libpurple-tcl | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| Red Hat:pidgin | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| Red Hat:pidgin-debuginfo | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| Red Hat:pidgin-devel | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| Red Hat:pidgin-docs | 0:2.7.9-5.el6.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| Red Hat:pidgin-perl | 0:2.6.6-11.el5.4 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- developer.pidgin.im/ticket/14884
- developer.pidgin.im/viewmtn/revision/diff/60f8379d0a610538cf42e0dd9ab1436c8b9308cd/with/3053d6a37cc6d8774aba7607b992a4408216adcd/libpurple/protocols/msn/oim.c
- developer.pidgin.im/viewmtn/revision/info/3053d6a37cc6d8774aba7607b992a4408216adcd
- pidgin.im/news/security/?id=61
- rhn.redhat.com/errata/RHSA-2012-1102.html
- secunia.com/advisories/50005
- www.mandriva.com/security/advisories?name=MDVSA-2012:029
- www.securityfocus.com/bid/52475
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A18019
Vendor advisories and official records. Exploit/PoC links are deliberately left out.