Buffer overflow in the XMPP SOCKS5 bytestream server in Pidgin (formerly Gaim) before 2.5.6 allows remote authenticated users to execute arb
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 90.9% of all records.
- Special conditions such as timing or configuration are required.
- Fixed version: pidgin (Debian:12) 2.5.6-1; pidgin (Debian:5.0) 2.4.3-4lenny2; pidgin (Red Hat:enterprise_linux:3::as) 0:1.5.1-3.el3.
Low priority for now. Upgrade to pidgin (Debian:12) 2.5.6-1; pidgin (Debian:5.0) 2.4.3-4lenny2; pidgin (Red Hat:enterprise_linux:3::as) 0:1.5.1-3.el3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Buffer overflow in the XMPP SOCKS5 bytestream server in Pidgin (formerly Gaim) before 2.5.6 allows remote authenticated users to execute arbitrary code via vectors involving an outbound XMPP file transfer. NOTE: some of these details are obtained from third party information.
- Published
- May 26, 2009
- Updated
- Jun 16, 2026
- EPSS
- 4.2% · 90th percentile
- CWE
- CWE-119
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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.5.5 inclusive
- pidgin pidgin2.0.0
- pidgin pidgin2.0.1
- pidgin pidgin2.0.2
- pidgin pidgin2.1.0
- pidgin pidgin2.1.1
- 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
- pidgin pidgin2.5.4
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.5.6-1 | 2.5.6-1 |
| Debian:5.0 | pidgin | before 2.4.3-4lenny2 | 2.4.3-4lenny2 |
| Red Hat:enterprise_linux:3::as | pidgin | before 0:1.5.1-3.el3 | 0:1.5.1-3.el3 |
| Red Hat:enterprise_linux:3::as | pidgin-debuginfo | before 0:1.5.1-3.el3 | 0:1.5.1-3.el3 |
| Red Hat:enterprise_linux:4::as | finch | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | finch-devel | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | libpurple | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | libpurple-devel | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | libpurple-perl | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | libpurple-tcl | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | pidgin | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | pidgin-debuginfo | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | pidgin-devel | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:4::as | pidgin-perl | before 0:2.5.5-2.el4 | 0:2.5.5-2.el4 |
| Red Hat:enterprise_linux:5::client | finch | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client | libpurple | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client | libpurple-perl | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client | libpurple-tcl | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client | pidgin-perl | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client_workstation | finch-devel | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client_workstation | libpurple-devel | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client_workstation | pidgin | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client_workstation | pidgin-debuginfo | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
| Red Hat:enterprise_linux:5::client_workstation | pidgin-devel | before 0:2.5.5-3.el5 | 0:2.5.5-3.el5 |
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
Published before and after this one in the same product
- ← EarlierCVE-2008-2927Jul 7, 2008 · Multiple integer overflows in the msn_slplink_process_msg functions in the MSN protocol handler in (1) libpurple/protocols/msn/slplink.c and28Monitor
- ← EarlierCVE-2008-3532Aug 8, 2008 · The NSS plugin in libpurple in Pidgin 2.4.3 does not verify SSL certificates, which makes it easier for remote attackers to trick a user int27Monitor
- Later →CVE-2009-1374May 26, 2009 · Buffer overflow in the decrypt_out function in Pidgin (formerly Gaim) before 2.5.6 allows remote attackers to cause a denial of service (app21Monitor
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.5.6-1 · Debian:12 | Package registry (OSV) |
| red hat:finch | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:finch-devel | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:libpurple | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:libpurple-devel | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:libpurple-perl | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:libpurple-tcl | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:pidgin | 0:1.5.1-3.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:pidgin-debuginfo | 0:1.5.1-3.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:pidgin-devel | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:pidgin-perl | 0:2.5.5-2.el4 · Red Hat:enterprise_linux:4::as | 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.
No commit or PR link among the references.
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
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:H/Au:S/C:C/I:C/A:C
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- secunia.com/advisories/35188
- secunia.com/advisories/35194
- secunia.com/advisories/35202
- secunia.com/advisories/35215
- secunia.com/advisories/35294
- secunia.com/advisories/35329
- secunia.com/advisories/35330
- www.gentoo.org/security/en/glsa/glsa-200905-07.xml
- www.mandriva.com/security/advisories?name=MDVSA-2009:140
- www.mandriva.com/security/advisories?name=MDVSA-2009:173
- www.pidgin.im/news/security/?id=29
- www.redhat.com/support/errata/RHSA-2009-1059.html
- www.redhat.com/support/errata/RHSA-2009-1060.html
- www.securityfocus.com/bid/35067
- www.ubuntu.com/usn/USN-781-1
- www.ubuntu.com/usn/USN-781-2
- www.vupen.com/english/advisories/2009/1396
- bugzilla.redhat.com/show_bug.cgi?id=500488
- exchange.xforce.ibmcloud.com/vulnerabilities/50682
Vendor advisories and official records. Exploit/PoC links are deliberately left out.